Date: Fri, 8 Mar 1996 13:23:48 +0100 (MET) From: torstenb@solar.tlk.com (Torsten Blum) To: peter@jhome.DIALix.COM (Peter Wemm) Cc: torstenb@tlk.com, asami@cs.berkeley.edu, coredump@nervosa.com, CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-ports@freefall.freebsd.org Subject: Re: cvs commit: ports/devel/libwww - Imported sources Message-ID: <m0tv1D2-00023GC@solar.tlk.com> In-Reply-To: <199603081204.UAA13192@jhome.DIALix.COM> from "Peter Wemm" at Mar 8, 96 08:03:59 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Wemm wrote: > >> * I don't think it makes much sense to put libwww into the www > >> * directory because its useless for joe-average-user. It does not > >> * contain any executables (like tiff or jpeg for example)... > >> > >> Um, whether it's useful for Joe FreeBSD user is not an issue here. We > >> never classified ports by skill level. :) > > > >I meant: it's only usefull for people who want to develop a www application > >with this particular library. > > > >autoconf, bcc, bison and so on are not useful for "Joe FreeBSD user" - that's > >why they are in the "devel" directory... > > And what happens when a program is written that uses this library comes > in as a port? You'd have to install the "developemnt" library in order > to use the final finished program? Yes, of course. Take a look at ssh and libz... > Take ports/www/comline for example.. It uses libwww-4.0D, and it's not a > development tool. A port that uses a library von ports/devel is not a development tool. We already have such a port: security/ssh depends on devel/libz > It's currently downloading and building it's own version of libwww-4.0D. Well, that's the problem with lots of the W3C Sources, they even use old versions (arena for example uses an old version of libwww whichis incompatible with the current version). > IMO, libwww should be in ports/www I don't agree with you. If you want to move libwww to the www category you have to do that with other ports (libz, m4 and so on) too... > and ports/www/comline should use it (if possible) rather than statically > compiling in "yet another" copy of the code. Yes, of course... -tb
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0tv1D2-00023GC>