On Saturday 22 December 2007 03:32:56 pm Edwin Groothuis wrote:
> On Sat, Dec 22, 2007 at 11:50:53AM -0600, Josh Paetzel wrote:
> > On Friday 21 December 2007 10:33:44 pm Edwin Groothuis wrote:
> > > On Fri, Dec 21, 2007 at 09:05:18PM -0600, Josh Paetzel wrote:
> > > > > > It also doesn't work if s
On Sat, Dec 22, 2007 at 11:50:53AM -0600, Josh Paetzel wrote:
> On Friday 21 December 2007 10:33:44 pm Edwin Groothuis wrote:
> > On Fri, Dec 21, 2007 at 09:05:18PM -0600, Josh Paetzel wrote:
> > > > > It also doesn't work if someone runs make rmconfig, or make config
> > > > > again and changes th
On Friday 21 December 2007 10:33:44 pm Edwin Groothuis wrote:
> On Fri, Dec 21, 2007 at 09:05:18PM -0600, Josh Paetzel wrote:
> > > > It also doesn't work if someone runs make rmconfig, or make config
> > > > again and changes things after the port is installed.
> > > >
> > > > It probably doesn't
> > That's why you do slave port with an option toggled, when you need a
> > package you can depend on. OPTIONS haven't changed this aspect.
>
> But you can't readily specify option X enabled, option Y disabled on
> that slave port.
You can, that's the point.
> There may come a time when it's
On Fri, Dec 21, 2007 at 09:05:18PM -0600, Josh Paetzel wrote:
> > > It also doesn't work if someone runs make rmconfig, or make config again
> > > and changes things after the port is installed.
> > >
> > > It probably doesn't work if a package was used to install either.
> >
> > Create a slave por
On Friday 21 December 2007 07:50:59 pm Edwin Groothuis wrote:
> On Fri, Dec 21, 2007 at 04:13:46PM -0600, Josh Paetzel wrote:
> > On Friday 21 December 2007 03:43:19 pm Edwin Groothuis wrote:
> > > On Fri, Dec 21, 2007 at 03:24:20PM -0600, Josh Paetzel wrote:
> > > > I've recently run across some b
On Fri, Dec 21, 2007 at 04:13:46PM -0600, Josh Paetzel wrote:
> On Friday 21 December 2007 03:43:19 pm Edwin Groothuis wrote:
> > On Fri, Dec 21, 2007 at 03:24:20PM -0600, Josh Paetzel wrote:
> > > I've recently run across some brokeness in ports that would be relatively
> > > trivial to deal with
On Saturday 22 December 2007 01:29:23 Pav Lucistnik wrote:
> Danny Pansters píše v so 22. 12. 2007 v 00:07 +0100:
> > How about e.g. LIB_DEPENDS=artsdsp:/usr/portss/[EMAIL PROTECTED] to
> > squash two
> > flies at once.
> >
> > The idea being that if the port is not installed it yet, it could be
>
> I bet most/many non-default ports don't get properly packaged anyway as
> it is.
I meant: ports with non-default OPTIONS. Sorry.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send a
--On December 22, 2007 12:07:45 AM +0100 Danny Pansters <[EMAIL PROTECTED]>
wrote:
I like the idea to do something with options. Optionifying ports is all
nice and well, but to make it meaningful, ports should be able to know
about each other's options. I actually have been working a bit on a
Danny Pansters píše v so 22. 12. 2007 v 00:07 +0100:
> How about e.g. LIB_DEPENDS=artsdsp:/usr/portss/[EMAIL PROTECTED] to
> squash two
> flies at once.
>
> The idea being that if the port is not installed it yet, it could be built
> with make WITHOUT_NAS=1 automagically. Something like this is
On Friday 21 December 2007 22:43:19 Edwin Groothuis wrote:
> On Fri, Dec 21, 2007 at 03:24:20PM -0600, Josh Paetzel wrote:
> > I've recently run across some brokeness in ports that would be relatively
> > trivial to deal with if one port had a way to know about the OPTIONS
> > another port was comp
On Friday 21 December 2007 03:43:19 pm Edwin Groothuis wrote:
> On Fri, Dec 21, 2007 at 03:24:20PM -0600, Josh Paetzel wrote:
> > I've recently run across some brokeness in ports that would be relatively
> > trivial to deal with if one port had a way to know about the OPTIONS
> > another port was c
On Fri, Dec 21, 2007 at 03:24:20PM -0600, Josh Paetzel wrote:
> I've recently run across some brokeness in ports that would be relatively
> trivial to deal with if one port had a way to know about the OPTIONS another
> port was compiled with.
I have been working on it a not-so-long-time-ago and
I've recently run across some brokeness in ports that would be relatively
trivial to deal with if one port had a way to know about the OPTIONS another
port was compiled with.
My initial thought was to register the state of OPTIONS in to /var/db/pkg.
This solves all of the problems that I know
15 matches
Mail list logo
