:I think this addresses the concerns of my initial (possibly
:poorly phrased) question. If you could do that then that would be great.
:
:Thanks.
Yah. It's in. It puts a Makefile in /usr containing easy targets and
directions for pkgsrc and src.
:Somewhat related to this topic, is there a reason that the
:installer isn't built from source along with a make world?
:--
:Dave Hayes - Consultant - Altadena CA, USA - [EMAIL PROTECTED]
Well, its on of those things that we are on fence for. Generally
speaking we do want to use pk
> What would be useful would be to create a /usr/pkgsrc/Makefile with
> some simple targets to acquire and maintain a pkgsrc tree so people
> don't have to go poking around figuring out how to get it. I will
> put something like that in place for this release since it will take
>
Matthew Dillon <[EMAIL PROTECTED]> writes:
> After this release I would also like to see a bit of a cleanup of
> the nrelease build, such as creating separate targets that just
> build make variables like WITH_INSTALLER instead of rollup targets
> (e.g. 'make installer release' inst
On Thu, 2 Aug 2007 00:36:32 -0400 (EDT)
"Justin C. Sherrill" <[EMAIL PROTECTED]> wrote:
>
> I agree with this - not including pkgsrc shrinks the size of the
> download, but it's still 80-something meg, and you end up using the
> bandwidth anyway pulling pkgsrc down through anoncvs, which also
> r
On Thu, Aug 02, 2007 at 12:36:32AM -0400, Justin C. Sherrill wrote:
> On Wed, August 1, 2007 11:34 pm, Matt Emmerton wrote:
> >
>
> > For pkgsrc, why couldn't we just include a recent snapshot of /usr/pkgsrc
> > on the CD (much like how FreeBSD provides a snapshot of /usr/ports). The
> > tree tha