Prev: Data files and ports
Next: deskutils/alexandria - why does it create a world readable and writable directory?
From: Alberto Villa on 11 Jun 2010 13:52
hi doug and list!
while upgrading libogg and libao (portmaster -x virtualbox -Rr libogg
libao) i've seen that some ports, which were already installed, got
reinstalled with a package. they're build dependencies of a port which
was upgraded, but they're also run dependencies of another one, so
they should be built from sources, given my portmaster.rc:

ALWAYS_SCRUB_DISTFILES=dopt
LOCAL_PACKAGEDIR=/usr/ports/packages
MAKE_PACKAGE=gopt
PM_DEL_BUILD_ONLY=pm_dbo
PM_INDEX=pm_index
PM_PACKAGES_BUILD=pmp_build

maybe they will also be deinstalled at the end, along with other build
dependencies... i'll see and report
--
Alberto Villa, FreeBSD committer <avilla(a)FreeBSD.org>
http://people.FreeBSD.org/~avilla
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Alberto Villa on 11 Jun 2010 14:41
On Friday 11 June 2010 19:52:12 Alberto Villa wrote:
> maybe they will also be deinstalled at the end, along with other build
> dependencies... i'll see and report

yes, they were deinstalled, even if required...
--
Alberto Villa, FreeBSD committer <avilla(a)FreeBSD.org>
http://people.FreeBSD.org/~avilla

"It's a summons."
"What's a summons?"
"It means summon's in trouble."
-- Rocky and Bullwinkle
From: Doug Barton on 11 Jun 2010 16:45
On 06/11/10 10:52, Alberto Villa wrote:
> hi doug and list!
> while upgrading libogg and libao (portmaster -x virtualbox -Rr libogg
> libao) i've seen that some ports, which were already installed, got
> reinstalled with a package. they're build dependencies of a port which
> was upgraded, but they're also run dependencies of another one,

The "build-only"ness of a port is calculated per portmaster run, so your
results are not unexpected, even if they are not desirable.

What needs to be done is to add code that tests whether ports marked
build only for a given portmaster run are also listed as dependencies in
an already installed port, but that's a non-trivial issue and my time
right now is dominated by trying to find work, which unfortunately
leaves little time available for portmaster hacking.

My only suggestion (which admittedly is inadequate) is to apply the
--delete-build-only knob on a case by case basis rather than having it
in portmaster.rc.


hth,

Doug

--

... and that's just a little bit of history repeating.
-- Propellerheads

Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Alberto Villa on 11 Jun 2010 18:56
On Friday 11 June 2010 22:45:26 Doug Barton wrote:
> The "build-only"ness of a port is calculated per portmaster run, so
your
> results are not unexpected, even if they are not desirable.
>
> What needs to be done is to add code that tests whether ports
marked
> build only for a given portmaster run are also listed as
dependencies in
> an already installed port,

i would suggest just checking if the port is already installed

> but that's a non-trivial issue and my time
> right now is dominated by trying to find work, which unfortunately
> leaves little time available for portmaster hacking.
>
> My only suggestion (which admittedly is inadequate) is to apply the
> --delete-build-only knob on a case by case basis rather than having
it
> in portmaster.rc.

don't worry! thank you for the answer, and keep focusing on your life
;)
--
Alberto Villa, FreeBSD committer <avilla(a)FreeBSD.org>
http://people.FreeBSD.org/~avilla

What do you have when you have six lawyers buried up to their necks
in sand?
Not enough sand.
From: Doug Barton on 12 Jun 2010 02:03
On 06/11/10 15:56, Alberto Villa wrote:
>
> i would suggest just checking if the port is already installed

That's not an adequate test because something could have been installed
as a build dependency previously, which means it could safely be deleted
with --delete-build-only.

However, this is your lucky day! I looked at the problem and it wasn't
as difficult as I first suspected. I've added code to the devel version
of portmaster, can you test it? You can get the information on
downloading it from svn at http://dougbarton.us/portmaster-proposal.html


Doug

--

... and that's just a little bit of history repeating.
-- Propellerheads

Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

 |  Next  |  Last
Pages: 1 2
Prev: Data files and ports
Next: deskutils/alexandria - why does it create a world readable and writable directory?