Date: Thu, 06 Sep 2001 12:05:37 -0700 (PDT) From: John Baldwin <jhb@FreeBSD.org> To: Alexander Langer <alex@big.endian.de> Cc: arch@FreeBSD.org Subject: RE: libh src/ import Message-ID: <XFMail.010906120537.jhb@FreeBSD.org> In-Reply-To: <20010906023247.A11776@zerogravity.kawo2.rwth-aachen.d>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06-Sep-01 Alexander Langer wrote: > Hi! > > How are peoples feelings about an import of libh into our src tree, > in order to push the development? As I said on IRC in an opinion that no one else seems to share, libh is useful in a wider regard than just FreeBSD, and I think it should be a separate project that gets vendor imported into src/contrib. Let's face it guys, FreeBSD doesn't have a lot of GUI people running around, and if libh is going to fly, it needs developers. IMHO, the best way to get developers for it is to not make it look like some FreeBSD-only thing, but instead to make it inviting to other developers. To that end, I think libh really belongs on Sourceforge as its own project, and something that goes in src/contrib along with Turbo Vision and Tcl when the time comes for it to replace sysinstall and hte package system. If it is imported directly into the tree and not into src/contrib, then it shouldn't go in src/release. Sysinstall didn't belong there, and no other code does either. It's a utility not only for installation, but also post-install configuration, thus the libs would need to be in src/lib/ and the binaries in src/usr.sbin or wherever. src/release would be the absolute worst place to put it. -- John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.010906120537.jhb>