Re: Custom builds from ports
On Tue, 31 Jul 2007, John Nielsen wrote:
On Tuesday 31 July 2007 12:16:32 pm CyberLeo Kitsana wrote:
Rakhesh Sasidharan wrote:
On Sun, July 29, 2007 01:37, N.J. Mann wrote:
In message <[EMAIL PROTECTED]>, CyberLeo Kitsana wrote:
Is there a way to specify which ports certain options are to be applied
to, without having to craft custom command lines and build ports
individually?
Is ports-mgmt/portconf what you are looking for?
I didn't know about ports-mgmt/portconf (will check it out now) but what
I use is the make.conf file.
This blog post
(http://blog.innerewut.de/articles/2006/01/14/upgrading-ports-and-preserv
e-mak e-options) is what enlightened me. And here's how the application
specific bits of my make.conf file looks:
.if ${.CURDIR:M*/shells/bash}
WITH_STATIC_BASH=yes
PREFIX=/
.endif
That's exactly what I was looking for.
Also, if you use portupgrade there's a MAKE_ARGS section
of /usr/local/etc/pkgtools.conf.
Yes, but the problem with sepcifying custom options in there is that
sometimes portupgrade ignores it. I don't know for a fact, but the blog
post I linked to above mentions so.
Say, bash and its dependency gettext have updates. And you have specified
some custom options for gettext in pkgtools.conf. If you upgrade gettext
directly using portupgrade, then these options get honoured. Instead, if
you upgrade bash and gettext gets upgraded as a result of that, then the
pkgtools.conf options are not honoured. So the only solution then is to
use the make.conf file coz that's always honoured. (From what I see, the
portconf tool too adds its stuff to the make.conf file).
Please correct me if I've understood wrong.
Regards,
Rakhesh
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Custom builds from ports
On Tuesday 31 July 2007 12:16:32 pm CyberLeo Kitsana wrote:
> Rakhesh Sasidharan wrote:
> > On Sun, July 29, 2007 01:37, N.J. Mann wrote:
> >> In message <[EMAIL PROTECTED]>, CyberLeo Kitsana wrote:
> >>> Is there a way to specify which ports certain options are to be applied
> >>> to, without having to craft custom command lines and build ports
> >>> individually?
> >>
> >> Is ports-mgmt/portconf what you are looking for?
> >
> > I didn't know about ports-mgmt/portconf (will check it out now) but what
> > I use is the make.conf file.
> >
> > This blog post
> > (http://blog.innerewut.de/articles/2006/01/14/upgrading-ports-and-preserv
> >e-mak e-options) is what enlightened me. And here's how the application
> > specific bits of my make.conf file looks:
> >
> > .if ${.CURDIR:M*/shells/bash}
> > WITH_STATIC_BASH=yes
> > PREFIX=/
> > .endif
> >
> > .if ${.CURDIR:M*/print/cups}
> > CUPS_OVERWRITE_BASE=yes
> > NO_LPR=yes
> > WITH_CUPS=yes
> > .endif
> >
> > .if ${.CURDIR:M*/databases/mysql50-*}
> > # these two options supposedly give a speed boost
> > BUILD_OPTIMIZED=yes
> > BUILD_STATIC=yes
> > .endif
> >
> > As you can see in the shells/bash case, I can even pass along PREFIX etc
> > arguments.
> >
> > Hope that helps.
>
> That's exactly what I was looking for.
Also, if you use portupgrade there's a MAKE_ARGS section
of /usr/local/etc/pkgtools.conf.
JN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Custom builds from ports
Rakhesh Sasidharan wrote:
> On Sun, July 29, 2007 01:37, N.J. Mann wrote:
>> In message <[EMAIL PROTECTED]>, CyberLeo Kitsana wrote:
>>> Is there a way to specify which ports certain options are to be applied
>>> to, without having to craft custom command lines and build ports
>>> individually?
>> Is ports-mgmt/portconf what you are looking for?
>
> I didn't know about ports-mgmt/portconf (will check it out now) but what I
> use is the make.conf file.
>
> This blog post
> (http://blog.innerewut.de/articles/2006/01/14/upgrading-ports-and-preserve-mak
> e-options) is what enlightened me. And here's how the application specific
> bits of my make.conf file looks:
>
> .if ${.CURDIR:M*/shells/bash}
> WITH_STATIC_BASH=yes
> PREFIX=/
> .endif
>
> .if ${.CURDIR:M*/print/cups}
> CUPS_OVERWRITE_BASE=yes
> NO_LPR=yes
> WITH_CUPS=yes
> .endif
>
> .if ${.CURDIR:M*/databases/mysql50-*}
> # these two options supposedly give a speed boost
> BUILD_OPTIMIZED=yes
> BUILD_STATIC=yes
> .endif
>
> As you can see in the shells/bash case, I can even pass along PREFIX etc
> arguments.
>
> Hope that helps.
That's exactly what I was looking for.
Thanks!
--
Fuzzy love,
-CyberLeo
Technical Administrator
CyberLeo.Net Webhosting
http://www.CyberLeo.Net
<[EMAIL PROTECTED]>
Furry Peace! - http://.fur.com/peace/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Custom builds from ports
On Sun, July 29, 2007 01:37, N.J. Mann wrote:
> In message <[EMAIL PROTECTED]>, CyberLeo Kitsana wrote:
>> Is there a way to specify which ports certain options are to be applied
>> to, without having to craft custom command lines and build ports
>> individually?
>
> Is ports-mgmt/portconf what you are looking for?
I didn't know about ports-mgmt/portconf (will check it out now) but what I
use is the make.conf file.
This blog post
(http://blog.innerewut.de/articles/2006/01/14/upgrading-ports-and-preserve-mak
e-options) is what enlightened me. And here's how the application specific
bits of my make.conf file looks:
.if ${.CURDIR:M*/shells/bash}
WITH_STATIC_BASH=yes
PREFIX=/
.endif
.if ${.CURDIR:M*/print/cups}
CUPS_OVERWRITE_BASE=yes
NO_LPR=yes
WITH_CUPS=yes
.endif
.if ${.CURDIR:M*/databases/mysql50-*}
# these two options supposedly give a speed boost
BUILD_OPTIMIZED=yes
BUILD_STATIC=yes
.endif
As you can see in the shells/bash case, I can even pass along PREFIX etc
arguments.
Hope that helps.
Regards,
Rakhesh
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Custom builds from ports
In message <[EMAIL PROTECTED]>, CyberLeo Kitsana wrote:
>
> My question concerns building ports with custom options.
>
> With some ports, 'make config' governs the options, and stores them in a
> file someplace so they are honored the next time you build or upgrade
> the port.
>
> With most ports, however, this is controlled by passing variables on the
> command line or via the environment.
>
> The most obvious location for these variables to be placed, so that they
> may affect recursive builds and upgrades, is make.conf. However, I've
> noticed that some ports use the same variable names for similar options
> ('WITH_MYSQL'), when I may not want that option set in both ports.
>
> Is there a way to specify which ports certain options are to be applied
> to, without having to craft custom command lines and build ports
> individually?
Is ports-mgmt/portconf what you are looking for?
Cheers,
Nick.
--
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Custom builds from ports
> Is there a way to specify which ports certain options are to be applied > to, without having to craft custom command lines and build ports > individually? Check out ports-mgmt/portconf, which allows you to set per-port options in a manner independent of which tool you use for installation and upgrades. -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller <[EMAIL PROTECTED]>' Key retrieval: Send an E-Mail to [EMAIL PROTECTED] E-Mail: [EMAIL PROTECTED] Web: http://www.scode.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Custom builds from ports
Hi!
My question concerns building ports with custom options.
With some ports, 'make config' governs the options, and stores them in a
file someplace so they are honored the next time you build or upgrade
the port.
With most ports, however, this is controlled by passing variables on the
command line or via the environment.
The most obvious location for these variables to be placed, so that they
may affect recursive builds and upgrades, is make.conf. However, I've
noticed that some ports use the same variable names for similar options
('WITH_MYSQL'), when I may not want that option set in both ports.
Is there a way to specify which ports certain options are to be applied
to, without having to craft custom command lines and build ports
individually?
Thanks!
--
Fuzzy love,
-CyberLeo
Technical Administrator
CyberLeo.Net Webhosting
http://www.CyberLeo.Net
<[EMAIL PROTECTED]>
Furry Peace! - http://.fur.com/peace/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
