Re: CVS removal from the base

There is also mirports from MirBSD that  is supported on MirBSD, MidnightBSD=
, and Mac OS X. They also got a pkgsrc port going recently. The problem is t=
hat projects have specific needs that other systems don't have. FreeBSD port=
s are by far the largest and very fast to build. Pkgsrc comes out quarterly s=
o it takes a long time to get patches in or updates as Dragonfly goes throug=
h. With MidnightBSD, we wanted all ports to go through fake install so our p=
ackages would work all the time and we could write package tools customized f=
or the ports tree.=20

Every BSD has different needs and different users.=20

Lucas Holt

On Dec 14, 2011, at 10:07 AM, "C. P. Ghost" <cpghost@cordula.ws> wrote:

> On Wed, Dec 14, 2011 at 2:00 PM, Julian H. Stacey <jhs@berklix.com> wrote:=

>> Maybe sometime we will see a project arise that will be a replacement
>> ports/ for more than one BSD, perhaps even extending to Linux, (to
>> avoid reinventing of the wheel that must go on with ports skeletal
>> structs for each OS) ( maybe with an RFC for a port/ skeleton struct
>> ?  If so, that may have ramifications on bits of src moved to ports.
>=20
> NetBSD's pkgsrc is already cross-OS (kind of), but it contains
> fewer ports than FreeBSD's ports collection:
>=20
> http://www.netbsd.org/docs/software/packages.html
>=20
>> Cheers,
>> Julian
>=20
> -cpghost.
>=20
> --=20
> Cordula's Web. http://www.cordula.ws/
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"=

_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"