From owner-freebsd-ports Wed Sep 6 14:23:35 2000 Delivered-To: freebsd-ports@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id D1FBD37B629; Wed, 6 Sep 2000 14:23:31 -0700 (PDT) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id D1DBE72C; Wed, 6 Sep 2000 14:23:30 -0700 (PDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id OAA25385; Wed, 6 Sep 2000 14:23:30 -0700 (PDT) Message-ID: <39B6B5D2.74219F2A@cup.hp.com> Date: Wed, 06 Sep 2000 17:23:30 -0400 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Satoshi - Ports Wraith - Asami Cc: obrien@FreeBSD.ORG, Akinori -Aki- MUSHA , ports@FreeBSD.ORG, marcel@FreeBSD.ORG Subject: Re: USE_LINUX? References: <200006070819.BAA14744@silvia.hip.berkeley.edu> <86u2f5zy3g.wl@localhost.local.idaemons.org> <20000607101234.A80031@dragon.nuxi.com> <39B5C330.6C1A9CE4@cup.hp.com> <39B5E487.53669CAD@cup.hp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Satoshi - Ports Wraith - Asami wrote: > > * Yes. Another option is /compat/linux/etc/redhat-release. I explicitly > * kept that file for these purposes (but don't care if it's not used :-). > * If such is needed in the future we can parse that file for the version > * number and complain if it's not appropriate for the port. > > It might be better if you change the filename to indicate different > versions if the need arises. The *_DEPENDS in bsd.port.mk can't read > the contents of the file. (Something like "redhat-release-6.1".) Well, the file is officially installed by one of the rpms and may be used by Linux native tools. A link containing the version number and pointing to that file is better. The link may point to anything for that matter. We might as well create a new file then. On second thought, forget about it; it's not worth it :-) > * Yes. I was thinking about why and when a port would need ldconfig and > * concluded that it likely doesn't need ldconfig until after it has > * installed the libraries. This of course means that a dependency on > * ldconfig for the build phase is wrong. If a port builds linux binaries > * from source, it depends on linux_devtools and BUILD_DEPENDS should > * contain something like gcc. If it downloads and installs a distribution, > * then BUILD_DEPENDS can be something like rpm, but not ldcondig. The > * install target will need a dependency on ldconfig or libc.so or whatever > * to make sure that linux_base is installed first. > * > * I think that the BUILD_DEPENDS should be empty by default. Only fFr the > * ports that depend on linux_devtools to work (linux_kdump for example), > * something like > * > * BUILD_DEPENDS = > * ${LINUXBASE}/usr/bin/gcc:${PORTSDIR}/devel/linux_devtools > * > * will do the trick. > > You mean there aren't any ports that depend *only* on linux_base that > needs the libraries (or anything else that it contains) for building? Not the libraries; ldconfig. If there's a port that depends on the libraries during build, it probably can do the work at install time as well (or of course add a proper BUILD_DEPENDS). For a default setting, BUILD_DEPENDS could be empty IMO. > For instance, isn't there something that will run its own binary > installer, that needs shared libraries? Yes. StarOffice, IIRC. But this will be covered by the RUN_DEPENDS, right? -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message