Date: Wed, 02 Apr 2008 10:39:36 +0200 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: <20080402103936.14106ai6f5p95ucc@webmail.leidinger.net> In-Reply-To: <05084110@bs1.sp34.ru> References: <07011489@ipt.ru> <20080321115227.zkcrs6rvc4c8s004@webmail.leidinger.net> <98037310@ipt.ru> <20080322085434.10838040@deskjail> <62336383@ipt.ru> <62213004@bs1.sp34.ru> <20080402080145.97672c008u0ewri8@webmail.leidinger.net> <05084110@bs1.sp34.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Boris Samorodov <bsam@ipt.ru> (from Wed, 02 Apr 2008 12:28:17 +0400)= : > On Wed, 02 Apr 2008 08:01:45 +0200 Alexander Leidinger wrote: >> Quoting Boris Samorodov <bsam@ipt.ru> (from Tue, 01 Apr 2008 =20 >> 20:42:27 +0400): >> > On Mon, 24 Mar 2008 00:36:00 +0300 Boris Samorodov wrote: >> >> On Sat, 22 Mar 2008 08:54:34 +0100 Alexander Leidinger wrote: >> > >> >> > Where do we have to introduce the *_PORT >> >> > stuff? Do we need a bsd.linux.mk, or can the bsd.linux-rpm.mk be use= d >> >> > for this? The strict answer may be no, but do we want to be =20 >> that strict? >> > >> >> Well, I'd prefer to use one existing file: bsd.linux-rpm.mk. If/when >> >> we use some other distro (I have some positive results with ubuntu) >> >> then may be we will have to use bsd.linux-deb.mk and split >> >> bsd.linux-rpm.mk into two files. But so far it's OK to me to use >> >> the existing one. >> > >> > Seems that I have change my mind since linux-rpm.mk is too tied to rpm >> > format and dealing with it. The file can't be (easily) used with an >> > average linux port. I tried to convert to using linux-rpm.mk acroread7 >> > port. I got a mess. :-( >> > >> > Well, what about new bsd.linux-apps.rpm? > >> I think we should keep the .mk at the end. > > Sure, it was a typo. > >> What about >> - bsd.port.mk which includes >> - bsd.linux.mk which includes >> - bsd.linux-rpm.mk (maybe conditionally) >> - bsd.linux-XXX.mk (maybe conditionally) > >> LINUX_OSRELEASE can be put into bsd.linux.mk. The USE_LINUX stuff can >> go into it too. > > Yep, fully agreed, this is our goal. But it will influence all linux > ports at once. While I try to use an evolition way with minimal > immediate impact to most linux ports. Almost as a Russian proverb says > "Drive slower, get farther". ;-) Oh, I was commenting on the final result. As an intermediate step you =20 can have bsd.linux.mk separate and don't include anything in it. If it =20 is ready, we can move from including it explicitly to including it =20 implicitly by asking portmgr to test a patch which adds linux.mk to =20 port.mk, adds linux-XXX.mk to linux.mk and removes linux-XXX.mk from =20 port.mk. Not a big deal, I think. Bye, Alexander. --=20 =09"And what will you do when you grow up to be as big as me?" asked the father of his little son. =09"Diet." 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?20080402103936.14106ai6f5p95ucc>