Date: Wed, 06 Sep 2000 17:23:30 -0400 From: Marcel Moolenaar <marcel@cup.hp.com> To: Satoshi - Ports Wraith - Asami <asami@FreeBSD.ORG> Cc: obrien@FreeBSD.ORG, Akinori -Aki- MUSHA <knu@idaemons.org>, ports@FreeBSD.ORG, marcel@FreeBSD.ORG Subject: Re: USE_LINUX? Message-ID: <39B6B5D2.74219F2A@cup.hp.com> References: <200006070819.BAA14744@silvia.hip.berkeley.edu> <86u2f5zy3g.wl@localhost.local.idaemons.org> <vqczooxn561.fsf@silvia.hip.berkeley.edu> <20000607101234.A80031@dragon.nuxi.com> <vqcg0ne9spn.fsf@silvia.hip.berkeley.edu> <39B5C330.6C1A9CE4@cup.hp.com> <vqclmx6w0e5.fsf@bubble.hip.berkeley.edu> <39B5E487.53669CAD@cup.hp.com> <vqcwvgpl41s.fsf@silvia.hip.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39B6B5D2.74219F2A>