Re: %_initscript??

["Mike A. Harris" <mharris meteng on ca>]

On Sun, 24 Sep 2000, Stan Bubrouski wrote:

>Date: Sun, 24 Sep 2000 10:09:14 -0400
>From: Stan Bubrouski <satan@fastdial.net>
>To: rpm-list@redhat.com
>Content-Type: text/plain; charset=us-ascii
>Subject: Re: %_initscript??
>
>Giulio Orsero wrote:
>
>> On Sat, 23 Sep 2000 20:29:55 -0400 (EDT), you wrote:
>>
>> >%_initdir or %_initscripts or something like that, where this
>> >macro expands to /etc/rc.d on Red Hat <= 6.2, and /etc on 7.0 and
>> >up.
>> AFAIK rh70 has initscripts in the same places of rh6.x.
>> It's just that there are synlinks added.
>> The change you are talking about maybe will be done in future versions.
>>
>
>No, Mike is right.  What was in previous /etc/rc.d/init.d is
>/etc/init.d and all the rc.X's are now in /etc too starting
>with 7.0.  One of the cool things about 7.0 is that alot of
>things that were previously unchanged to avoid confilict are
>now being changed, and I for one am glad.  FHS compliance is a
>good thing.  Other linux distributions are starting to follow
>FHS compliance like Debian which would make RPM packages

Yeah, I'm glad to see standards compliance, and I want to follow
standards as well, however I do not want to throw away
compatibility with distributions that aren't FHS compliant, and I
don't want to rely on symlinks being present either.

>easier to install because the paths should be very much the
>same on all the systems. I think if a macro was added for each
>dir mentioned in the latest FHS to rpm it would be really
>helpful in distributing packages on many different linux
>distributions that support FHS compliance.  That was just my
>3.14159 cents worth.

Yep, I agree.  However if RPM does not have such a macro, adding
it will be nice, but still wont help me since it would require
that every user upgrade RPM first before installing my
packages.  So in that case, I would have to write my own RPM
non-specific way of determining where initscripts reside.  Any
suggestions?

I could test /etc/redhat-release, but that assumes that it is
there, and only works on Red Hat systems.  If there isn't an easy
way of determining where initscripts should go though, I'll take
the Red Hat specific way first since it is the most used dist,
and is my primary support target.

TIA


--
         Mike A. Harris  -  Linux advocate  -  Open source advocate
                   Copyright 2000 all rights reserved
                               ----------
#[Mike A. Harris bash tip #2 - custom colorized bash prompts]
# For a color prompt, put the following at the bottom of your ~/.bash_profile
TTYNAME=$(tty | sed -e 's/^\/dev\///' -e 's/^tty//');DRED=31;DGREEN=32
BROWN=33;DBLUE=34;DMAGENTA=35;DCYAN=36;GREY=37;DGREY=30\;1;RED=31\;1
GREEN=32\;1;YELLOW=33\;1;BLUE=34\;1;MAGENTA=35\;1;CYAN=36\;1;WHITE=37\;1
CLRUSER=$CYAN ; CLRHOST=$YELLOW   # Set the user and host colors here
PS1="$TTYNAME \[\033[${CLRUSER}m\]\u\[\033[0;m\]"
export PS1="${PS1}@\[\033[${CLRHOST}m\]\h\\[\033[0;m\]:\w\$ "