Re: port variants
On Sat, 14 Apr 2012 05:00:34 -0700 per...@pluto.rain.com wrote: > Kevin Oberman wrote: > > > While I think makefile-options is the way to go, I should also > > point out that for the specific case of emacs and X11, it is > > not used due to the very large differences. Other "variants" > > are handled via options, but there are separate emacs and > > emacs-nox11 ports. > > ... > > The port maintainer/developer has to make a call as to which > > approach is more practical, but I suspect portmgr@ will press > > for maximum use of makefile-options. Unfortunately we can't force anyone to use OPTIONS. Yet. I hope things will change once we get OPTIONS-NG in, since the new framework will address (AFAIK) all the objections people have against our current OPTIONS. > One reason to use a slave port instead of an option is so that both > configurations will be routinely build-tested, and corresponding > packages made available. Any one port can have only one "default" > configuration. Yes. We're lagging behind in this area. With the new OPTIONS and the next iteration of pkgNG, this will be hopefully solved. BUt it will take at least a year. -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: port variants
On 13 April 2012 23:38, Kevin Oberman wrote: > 2012/4/13 Konstantin Tokarev : >> 13.04.2012, 23:55, "Chris Inacio" : >>> On Apr 13, 2012, at 3:39 PM, Freddie Cash wrote: >>> On Fri, Apr 13, 2012 at 12:04 PM, Chris Inacio wrote: > I was recently asked to do some FreeBSD ports support work. I mostly > use a > Mac and the MacPorts system. MacPorts has the concept of a variant for a > port, but I can't find the analogue in the FreeBSD system. > > Does the FreeBSD ports system have the concept of a variant? If so, can > someone point me in the right direction on how to create one? Describing what a "variant" is, how it works in MacPorts, and what you are trying to do would help a lot. :) The closest guess I could make would be "slave port", but I don't think that works the same way. >>> >>> Sorry, you're right. >>> >>> For example, a port of say Emacs could have a variant of X11. >>> >>> So Emacs or Emacs+X11. >>> >>> The X11 variant would (somewhat obviously) include building regular Emacs >>> but also the X11 toolbar etc. while Emacs wouldn't include any X11 features >>> (& dependencies). >>> >>> On the Mac, we can build universal binaries (PowerPC, ia32, and x86_64), at >>> the cost of disk space. So we can build almost any package with the >>> +universal variant. >>> >>> Is that a reasonable explanation? >> >> Seems like you need makefile options: >> >> http://www.freebsd.org/doc/en/books/porters-handbook/makefile-options.html > > While I think makefile-options is the way to go, I should also point > out that for the specific case of emacs and X11, it is not used due to > the very large differences. Other "variants" are handled via options, > but there are separate emacs and emacs-nox11 ports. > > Most obviously, all of the emacs options are X11 related and there is > no way that I know to have two sets of options with one list dependent > on the other. If there are only a coupe of cases of this, it may be > noted on the options like: > THREADS " Build with thread support" > On \ > FOO "Foo support (requires THREADS)" > OFF \ > > The port maintainer/developer has to make a call as to which approach > is more practical, but I suspect portmgr@ will press for maximum use > of makefile-options. It's unusual for portmgr to intervene in individual ports-- if the maintainer takes the trouble to make test and support OPTIONS, then great, but it's by no means mandatory. It's better to be slightly less flexible than have loads of OPTIONS which break other ports in subtle ways. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: port variants
Kevin Oberman wrote: > While I think makefile-options is the way to go, I should also > point out that for the specific case of emacs and X11, it is > not used due to the very large differences. Other "variants" > are handled via options, but there are separate emacs and > emacs-nox11 ports. > ... > The port maintainer/developer has to make a call as to which > approach is more practical, but I suspect portmgr@ will press > for maximum use of makefile-options. One reason to use a slave port instead of an option is so that both configurations will be routinely build-tested, and corresponding packages made available. Any one port can have only one "default" configuration. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: port variants
2012/4/13 Konstantin Tokarev : > > > 13.04.2012, 23:55, "Chris Inacio" : >> On Apr 13, 2012, at 3:39 PM, Freddie Cash wrote: >> >>> On Fri, Apr 13, 2012 at 12:04 PM, Chris Inacio wrote: I was recently asked to do some FreeBSD ports support work. I mostly use a Mac and the MacPorts system. MacPorts has the concept of a variant for a port, but I can't find the analogue in the FreeBSD system. Does the FreeBSD ports system have the concept of a variant? If so, can someone point me in the right direction on how to create one? >>> Describing what a "variant" is, how it works in MacPorts, and what you >>> are trying to do would help a lot. :) >>> >>> The closest guess I could make would be "slave port", but I don't >>> think that works the same way. >> >> Sorry, you're right. >> >> For example, a port of say Emacs could have a variant of X11. >> >> So Emacs or Emacs+X11. >> >> The X11 variant would (somewhat obviously) include building regular Emacs >> but also the X11 toolbar etc. while Emacs wouldn't include any X11 features >> (& dependencies). >> >> On the Mac, we can build universal binaries (PowerPC, ia32, and x86_64), at >> the cost of disk space. So we can build almost any package with the >> +universal variant. >> >> Is that a reasonable explanation? > > Seems like you need makefile options: > > http://www.freebsd.org/doc/en/books/porters-handbook/makefile-options.html While I think makefile-options is the way to go, I should also point out that for the specific case of emacs and X11, it is not used due to the very large differences. Other "variants" are handled via options, but there are separate emacs and emacs-nox11 ports. Most obviously, all of the emacs options are X11 related and there is no way that I know to have two sets of options with one list dependent on the other. If there are only a coupe of cases of this, it may be noted on the options like: THREADS " Build with thread support" On \ FOO"Foo support (requires THREADS)" OFF \ The port maintainer/developer has to make a call as to which approach is more practical, but I suspect portmgr@ will press for maximum use of makefile-options. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: port variants
13.04.2012, 23:55, "Chris Inacio" : > On Apr 13, 2012, at 3:39 PM, Freddie Cash wrote: > >> On Fri, Apr 13, 2012 at 12:04 PM, Chris Inacio wrote: >>> I was recently asked to do some FreeBSD ports support work. I mostly use a >>> Mac and the MacPorts system. MacPorts has the concept of a variant for a >>> port, but I can't find the analogue in the FreeBSD system. >>> >>> Does the FreeBSD ports system have the concept of a variant? If so, can >>> someone point me in the right direction on how to create one? >> Describing what a "variant" is, how it works in MacPorts, and what you >> are trying to do would help a lot. :) >> >> The closest guess I could make would be "slave port", but I don't >> think that works the same way. > > Sorry, you're right. > > For example, a port of say Emacs could have a variant of X11. > > So Emacs or Emacs+X11. > > The X11 variant would (somewhat obviously) include building regular Emacs but > also the X11 toolbar etc. while Emacs wouldn't include any X11 features (& > dependencies). > > On the Mac, we can build universal binaries (PowerPC, ia32, and x86_64), at > the cost of disk space. So we can build almost any package with the > +universal variant. > > Is that a reasonable explanation? Seems like you need makefile options: http://www.freebsd.org/doc/en/books/porters-handbook/makefile-options.html -- Regards, Konstantin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: port variants
On Apr 13, 2012, at 3:39 PM, Freddie Cash wrote: > On Fri, Apr 13, 2012 at 12:04 PM, Chris Inacio wrote: >> I was recently asked to do some FreeBSD ports support work. I mostly use a >> Mac and the MacPorts system. MacPorts has the concept of a variant for a >> port, but I can't find the analogue in the FreeBSD system. >> >> Does the FreeBSD ports system have the concept of a variant? If so, can >> someone point me in the right direction on how to create one? > > Describing what a "variant" is, how it works in MacPorts, and what you > are trying to do would help a lot. :) > > The closest guess I could make would be "slave port", but I don't > think that works the same way. > Sorry, you're right. For example, a port of say Emacs could have a variant of X11. So Emacs or Emacs+X11. The X11 variant would (somewhat obviously) include building regular Emacs but also the X11 toolbar etc. while Emacs wouldn't include any X11 features (& dependencies). On the Mac, we can build universal binaries (PowerPC, ia32, and x86_64), at the cost of disk space. So we can build almost any package with the +universal variant. Is that a reasonable explanation? Chris > -- > Freddie Cash > fjwc...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: port variants
Freddie Cash wrote on 13.04.2012 23:39: On Fri, Apr 13, 2012 at 12:04 PM, Chris Inacio wrote: I was recently asked to do some FreeBSD ports support work. I mostly use a Mac and the MacPorts system. MacPorts has the concept of a variant for a port, but I can't find the analogue in the FreeBSD system. Does the FreeBSD ports system have the concept of a variant? If so, can someone point me in the right direction on how to create one? Describing what a "variant" is, how it works in MacPorts, and what you are trying to do would help a lot. :) The closest guess I could make would be "slave port", but I don't think that works the same way. http://guide.macports.org/chunked/reference.variants.html Chris, the job needed should be described in more detail, but at glance options framework - it's what you looking for [1]. [1] http://www.freebsd.org/doc/en/books/porters-handbook/book.html#MAKEFILE-OPTIONS -- Regards, Ruslan Tinderboxing kills... the drives. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: port variants
On Fri, Apr 13, 2012 at 12:04 PM, Chris Inacio wrote: > I was recently asked to do some FreeBSD ports support work. I mostly use a > Mac and the MacPorts system. MacPorts has the concept of a variant for a > port, but I can't find the analogue in the FreeBSD system. > > Does the FreeBSD ports system have the concept of a variant? If so, can > someone point me in the right direction on how to create one? Describing what a "variant" is, how it works in MacPorts, and what you are trying to do would help a lot. :) The closest guess I could make would be "slave port", but I don't think that works the same way. -- Freddie Cash fjwc...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
