From: Helmut Schaa <helmut.schaa@googlemail.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Helmut Schaa <helmut.schaa@googlemail.com>,
Luis Rodriguez <Luis.Rodriguez@atheros.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wireless-regdb: add example spec file
Date: Sun, 25 Jan 2009 11:41:26 +0100 [thread overview]
Message-ID: <200901251141.27669.helmut.schaa@gmail.com> (raw)
In-Reply-To: <20090124203746.GB22475@tesla>
Am Samstag, 24. Januar 2009 schrieb Luis R. Rodriguez:
> On Sat, Jan 24, 2009 at 03:27:48AM -0800, Helmut Schaa wrote:
> > Am Samstag, 24. Januar 2009 schrieb Luis R. Rodriguez:
> > > This is a simple example spec file which can be used
> > > by RPM distributions. Note that the man page isn't yet
> > > installed as it has not yet been commited.
> > >
> > > Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
> > > ---
> >
> > [...]
> >
> > > +%install
> > > +install -m 755 -d %buildroot/%crda_lib
> > > +install -m 644 regulatory.bin %buildroot/%{crda_lib}/regulatory.bin
> >
> > Why not make use of "make DESTDIR=%buildroot install" here?
>
> Since its in the spec file you have direct control over that, what would
> be best is to get wireless-regdb makefile to use DESTDIR and then just
> have the spec file call make install. I sent the patch for the first part
> already, so the spec file can be changed once that goes in.
Yes, I saw your patch that allows DESTDIR usage and was just wondering why
not make use of it.
Thanks,
Helmut
prev parent reply other threads:[~2009-01-25 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 23:16 [PATCH] wireless-regdb: add example spec file Luis R. Rodriguez
2009-01-24 11:27 ` Helmut Schaa
2009-01-24 20:37 ` Luis R. Rodriguez
2009-01-25 10:41 ` Helmut Schaa [this message]
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=200901251141.27669.helmut.schaa@gmail.com \
--to=helmut.schaa@googlemail.com \
--cc=Luis.Rodriguez@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.