linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@cse.unsw.edu.au>
To: bluca@comedia.it
Cc: linux-raid@vger.kernel.org
Subject: Re: ANNOUNCE - mdadm 0.8 - candidate for 1.0
Date: Wed, 10 Apr 2002 11:05:07 +1000 (EST)	[thread overview]
Message-ID: <15539.36803.487505.398985@notabene.cse.unsw.edu.au> (raw)
In-Reply-To: message from Luca Berra on Sunday April 7

On Sunday April 7, bluca@comedia.it wrote:
> On Thu, Apr 04, 2002 at 02:55:43PM +1000, Neil Brown wrote:
> > Yes... I sort of noticed that in passing...
> > 
> > I added:
> >    %_sbindir /sbin
> >    %_sysconfdir /etc
> > 
> > to my .rpcmacros and rebuild the rpms so they now put files in the
> > "right" places.
> > 
> > Any  RPM gurus want to suggest what I *should* do?
> i am no guru but an alterantive seems to be setting
> %define _exec_prefix %{nil}
> in the spec file

Thanks.  This looks like a reasonable suggestion.  And it seems to work.
> 
> > Is it wrong to use %_sbindir and $_sysconfdir ???
> i believe common practice is using /sbin literaly in the
> spec file, but i prefer the above thing
> 
> %_sysconfdir should be set to /etc in the per platform rpm macro file
> /usr/lib/rpm/%{_target_cpu}-%{_vendor}-%{_target_os}
> ie: /usr/lib/rpm/i386-redhat-linux

Hmmm. and debian's /usr/lib/rpm files set it to /usr/etc which doesn't
exist on debian :-(  I'll just assume that debian is broken and leave
_sysconfdir set to /etc in my .rpmmacros.

Thanks again,
NeilBrown

  reply	other threads:[~2002-04-10  1:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15531.46606.314167.19186@notabene.cse.unsw.edu.au>
     [not found] ` <Pine.GSO.4.21.0204032025070.9004-100000@gecko.roadtoad.net>
     [not found]   ` <15531.56527.518603.63636@notabene.cse.unsw.edu.au>
2002-04-07 12:56     ` ANNOUNCE - mdadm 0.8 - candidate for 1.0 Luca Berra
2002-04-10  1:05       ` Neil Brown [this message]
     [not found]         ` <20020410203945.99811.qmail@web10405.mail.yahoo.com>
2002-04-10 23:57           ` Neil Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15539.36803.487505.398985@notabene.cse.unsw.edu.au \
    --to=neilb@cse.unsw.edu.au \
    --cc=bluca@comedia.it \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).