Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Feb 2013 08:12:13 -0500
From:      "Mikhail T." <mi+thun@aldan.algebra.com>
To:        Tom Evans <tevans.uk@googlemail.com>
Cc:        Kimmo Paasiala <kpaasial@gmail.com>, "free >> Current FreeBSD" <freebsd-current@freebsd.org>, "O. Hartmann" <ohartman@zedat.fu-berlin.de>, Ports FreeBSD <freebsd-ports@freebsd.org>, Yamaya Takashi <yamayan@kbh.biglobe.ne.jp>
Subject:   Re: ports include /etc/src.conf? i.e. graphics/libfpx
Message-ID:  <511CE2AD.8050506@aldan.algebra.com>
In-Reply-To: <CAFHbX1LKuDbKYSifFDsRYhc3eCd5g7c-ifAHF9jMSjqow6kVVA@mail.gmail.com>
References:  <511B662C.7030602@zedat.fu-berlin.de> <511B874A.7080901@kbh.biglobe.ne.jp> <CAFHbX1Lg4w8g30DrcEbvm%2B6sFvTDpRAt7OouBBBUs1iiMaEL5g@mail.gmail.com> <CA%2B7WWSfOHnYow56BggaG6_T8hGY9GZKTzuT_E7=LWex2Th0XQQ@mail.gmail.com> <511BBDAD.1080806@zedat.fu-berlin.de> <511CD83C.107@aldan.algebra.com> <CAFHbX1LKuDbKYSifFDsRYhc3eCd5g7c-ifAHF9jMSjqow6kVVA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
14.02.2013 08:02, Tom Evans написав(ла):
> I think src.conf is meant only to be included when building src. For
> example, bsd.port.mk sets _WITHOUT_SRCCONF before including bsd.own.mk
> (which is the makefile that includes src.conf). It's done this since
> src.conf was added in 2006, so evidently ports are, by design, not
> supposed to include src.conf. 
Awesome. All that's missing then, is for _WITHOUT_SRCCONF to be
automatically added to MAKE_ENV...
>>> I would consider them broken!
>> On the contrary. I wish, more ports were using the system's bsd.*.mk
>> collection -- instead of the godawful autoconf, for example.
> Er? What port uses autoconf for driving the building the port? A lot
> of ports have build systems that use autoconf, but determining how to
> build is always driven by *.mk.
>
> I don't think part of porting to FreeBSD should be rewriting how the
> package builds itself.
Hundreds of ports rely on auto-something bundled with the vendor's
sources, that's what I meant. As for how to build a particular package,
that's up to the port-maintainer.
> Either the documentation is wrong, and should be changed, or this
> singular port is not behaving as it should.
I may sound defensive here, but I'll still repeat, that "this singular
port" (and I do, in fact, have other ones like it) started using
bsd.lib.mk 5 years before src.conf (and its man-page) was added to the tree.

    -mi




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?511CE2AD.8050506>