--On November 30, 2012 7:07:20 PM +0100 Alberto Villa
wrote:
On Fri, Nov 30, 2012 at 4:47 PM, Thierry Thomas
wrote:
However, to enforce the right dependency, this option have to produce a
different plist.
Really? Isn't enough to depend on the package name instead of a file?
No. The depe
Le ven 30 nov 12 à 19:07:20 +0100, Alberto Villa
écrivait :
> On Fri, Nov 30, 2012 at 4:47 PM, Thierry Thomas wrote:
> > However, to enforce the right dependency, this option have to produce a
> > different plist.
>
> Really? Isn't enough to depend on the package name instead of a file?
xxx_DE
On Fri, Nov 30, 2012 at 4:47 PM, Thierry Thomas wrote:
> However, to enforce the right dependency, this option have to produce a
> different plist.
Really? Isn't enough to depend on the package name instead of a file?
--
Alberto Villa, FreeBSD committer
http://people.FreeBSD.org/~avilla
--On November 30, 2012 4:47:40 PM +0100 Thierry Thomas
wrote:
Hello,
Le ven 30 nov 12 à 16:36:32 +0100, Paul Schmehl
écrivait :
I'm working on a port that has an option for a build_depends on another
port. If that option is selected, the dependent port MUST be built with
an option that i
Thierry Thomas wrote:
> Hello,
>
> Le ven 30 nov 12 à 16:36:32 +0100, Paul Schmehl
> écrivait :
> > I'm working on a port that has an option for a build_depends on
> > another port. If that option is selected, the dependent port MUST
> > be built with an option that is not selected by default.
Hello,
Le ven 30 nov 12 à 16:36:32 +0100, Paul Schmehl
écrivait :
> I'm working on a port that has an option for a build_depends on another
> port. If that option is selected, the dependent port MUST be built with an
> option that is not selected by default.
>
> Is there a way to either forc
I'm working on a port that has an option for a build_depends on another
port. If that option is selected, the dependent port MUST be built with an
option that is not selected by default.
Is there a way to either force that option to be selected in the dependent
port? Or, failing that, is it
