Date: Tue, 25 Jul 2000 01:04:00 -0700 From: W Gerald Hicks <jhix@mindspring.com> To: "Jeffrey S. Sharp" <jss@subatomix.com> Cc: freebsd-small@FreeBSD.ORG Subject: Re: TinyBSD kit progress report Message-ID: <200007250804.BAA06013@mindspring.com> In-Reply-To: Your message of "Tue, 25 Jul 2000 01:17:58 CDT." <Pine.BSF.4.21.0007250101060.8192-100000@lepton.subatomix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > It seems to me that it would be a lot more interesting to have the
> > ports/build frameworks set up to accomodate building "these things"
> > out of the src/ tree.
> > ...
> > ports/itsybsd anyone? :-)
> Interesting idea, but there are some things about small freebsd kits
> that are tightly coupled to the underlying system.
Exactly and it's just this coupling I would like to see our collective
energies invested into removing instead of heading down the path of
a redux of our picobsd experience.
Some time ago I submitted an experimental patch which allowed ports to
fetch their sources via CVS. This allows the construction of aribitrary
source trees from divergent branches and possibly even from other projects.
I used this ugly little hack for my own small-freebsd variant (FleaBSD)
> Imagine the differences introduced when installing the port onto
> systems from different branches... Sure, we could make it happen
> with some Makefile/patch magic, but having the kit in src/release
> seems like the simpler solution IMHO.
I've been through the issues in depth, they aren't insurmountable. The
most difficult part of something like this will be gaining a consensus
as to how we should approach it. Another issue is to convince the mainline
developers to consider the small-bsd variants when adding new features
to the mainline development.
Since Andrzej has moved on to other things it seems to me that the few
interested committers have mostly introduced their own biases and desires
onto the subtree with little regard for how people were actually using
PicoBSD. (To be fair, some of the work was done thoughtfully and with
a broad vision).
Right now I think it's fair to say that PicoBSD is a festering mess and
that the current development model isn't working very well. Reproducing
that model doesn't seem to be the right approach to me.
All that and I *like* {Tiny,Pico}BSD :-)
Cheers,
Jerry Hicks
jhix@mindspring.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-small" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200007250804.BAA06013>