add LINUX_OSRELEASE to bsd.linux-rpm.mk

[Boris Samorodov]

On Wed, 02 Apr 2008 08:01:45 +0200 Alexander Leidinger wrote:
> Quoting Boris Samorodov <bsam at ipt.ru> (from Tue, 01 Apr 2008 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 used
> >> > for this? The strict answer may be no, but do we want to be 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". ;-)


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve