Date: Fri, 21 Mar 2008 11:52:27 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: Boris Samorodov <bsam@ipt.ru> Cc: freebsd-emulation@FreeBSD.org Subject: Re: add LINUX_OSRELEASE to bsd.linux-rpm.mk Message-ID: <20080321115227.zkcrs6rvc4c8s004@webmail.leidinger.net> In-Reply-To: <07011489@ipt.ru> References: <07011489@ipt.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Boris Samorodov <bsam@ipt.ru> (from Fri, 21 Mar 2008 02:25:50 +0300)= : > Hello, > > > We are approching a day when two default compat.linux.osrelease > would exist (though it would be a one per branch). There should be a > way to determine which linux infrastructure ports should be > installed and a way to override this value (e.g. while package > building). > > I propose the following patch to bsd.linux-rpm.mk. It introduces a new > variable LINUX_OSRELEASE which is evaluated at bsd.linux-rpm.mk unless > it has been already defined. > > What do you think? What's the big picture (in the sense of: how do you want to use it)? Depending on the usage, it may be overkill to use it in linux-rpm.mk =20 and it would be better to just use it directly when it is needed. If =20 you want to use it in nearly every linux port, then sure, go ahead. =20 But if it is just a handful of ports, I would like to understand the =20 implications. If you have something which uses this already, just show =20 it. If not, I would say we are not in a hurry to add this now and we =20 can talk about it, if there's something to show. Bye, Alexander. --=20 A man paints with his brains and not with his hands. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080321115227.zkcrs6rvc4c8s004>