[CFT] add a config.site cache for the ports

Jeremy Messenger mezz.freebsd at gmail.com
Mon Mar 18 19:35:51 UTC 2013


On Mar 18, 2013 2:24 PM, "Baptiste Daroussin" <bapt at freebsd.org> wrote:
>
> On Mon, Mar 18, 2013 at 02:15:51PM -0500, Jeremy Messenger wrote:
> > On Mar 18, 2013 12:42 PM, "Baptiste Daroussin" <bapt at freebsd.org> wrote:
> > >
> > > Hi,
> > >
> > > The autotools allows us to have a config.site cache where we define
our
> > defaults
> > > values for a couple of things, and prevent the "slow" and possibly
wrong
> > > autodetection.
> > >
> > > Here is a patch that makes use of it:
> > > http://people.freebsd.org/~bapt/autotools_config_site.diff
> > >
> > > As the libiconv/gettext update has shown the configure scripts can
fall
> > back on
> > > gnu version of commands first if it find it, and in case gettext is
> > removed you
> > > can get trouble.
> > >
> > > In this config.site, I hardcoded a couple of FreeBSD binaries in
order to
> > always
> > > use them, but I let the toolchain being autodetected.
> > >
> > > I also added a couple of headers to avoid useless checks and more can
be
> > added
> > > in the futur.
> > >
> > > Any thought?
> >
> > There are some ports that need to use gnu tar, gnu sed, gnu grep and
other
> > gnu stuff. How will this cache affect on those ports?
> >
> > > regards,
> > > Bapt
>
> We can always overwrite those in CONFIGURE_ENV if needed, and I'll run an
> exp-run to make sure no ports requiring gsed, gtar etc fails.

If it works very well then I think it sounds good.

> regards,
> Bapt


More information about the freebsd-ports mailing list