From: John Kacur <jkacur@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: trace-cmd: make Makefile rpm-friendly
Date: Mon, 19 Apr 2010 22:06:23 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1004192200570.4111@localhost.localdomain> (raw)
In-Reply-To: <1271703972.10448.5.camel@gandalf.stny.rr.com>
On Mon, 19 Apr 2010, Steven Rostedt wrote:
> On Mon, 2010-04-19 at 20:11 +0200, John Kacur wrote:
> >
> > On Mon, 19 Apr 2010, Randy Dunlap wrote:
> >
> > > From: Randy Dunlap <randy.dunlap@oracle.com>
> > >
> > > Update Makefile to support rpmbuild DESTDIR usage.
> >
> > So, what would happen if you did
> > make DESTDIR=/usr/local install ?
> >
> > I think you would get /usr/local/usr/local
> > So, I think I would NAK this patch.
> >
> > I also don't believe there is anything magical about DESTDIR in a spec
> > file. Essentially, prefix in this makefile is equivalent to DESTDIR, so
> > you can replace DESTDIR with prefix in a spec template.
> >
>
> NAK is too strong. I was looking at what perf does, and it basically
> makes prefix and DESTDIR the same.
>
> ifndef DESTDIR
> prefix = $(HOME)
> endif
>
> We could do..
>
> ifndef DESDIR
> prefix = /usr/local/bin
> endif
>
> and then, if DESTDIR is not set, it would do the right thing.
>
Yeah, the above is actually an unsatisfactory workaround.
see 7ae5f21361fea11f58c398701da635f778635d13
Another solution is to not copy obfuscated Makefiles when starting new
projects!
/me runs away
next prev parent reply other threads:[~2010-04-19 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 17:00 Randy Dunlap
2010-04-19 18:11 ` John Kacur
2010-04-19 18:38 ` Randy Dunlap
2010-04-19 19:06 ` Steven Rostedt
2010-04-19 19:09 ` Randy Dunlap
2010-04-19 20:06 ` John Kacur [this message]
2010-04-19 20:15 ` Randy Dunlap
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=alpine.LFD.2.00.1004192200570.4111@localhost.localdomain \
--to=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®