linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>, linux-can@vger.kernel.org
Subject: Re: [PATCH can-utils] Don't overwrite PREFIX and DESTDIR when provided via the environment
Date: Sun, 18 Aug 2013 22:49:30 +0200	[thread overview]
Message-ID: <20130818204930.GM30496@pengutronix.de> (raw)
In-Reply-To: <5210A9C5.5070309@hartkopp.net>

On Sun, Aug 18, 2013 at 01:02:29PM +0200, Oliver Hartkopp wrote:
> On 17.08.2013 21:32, Marc Kleine-Budde wrote:
> > On 08/17/2013 09:28 PM, Uwe Kleine-König wrote:
> >> For creating a Debian package providing PREFIX and DESTDIR via the
> >> environment is the easiest option. So use ?= to assign these two
> >> variables to honor the values in the environment.
> > 
> > I suggest to use autotools.
> > 
> > ./configure && make && make install
> > 
> 
> Today i like the possibility to use autotools or just to say 'make && make
> install' without autotools.
> 
> You may choose for the Debian package the build process which is more appropriate.
> 
> >
> > -DESTDIR =
> > -PREFIX = /usr/local
> > +DESTDIR ?=
> > +PREFIX ?= /usr/local
> >
> 
> 1. good idea - I already pushed it to the git tree
Thanks, but you somehow messed up the attribution. All three patches I
sent in the last few days appear with author=you :-(

> 2. I wonder if we should doublecheck the target directories when making it a
> real Debian package
> 
> e.g. the majority of tools should go into /usr/bin then
> 
> But some tools that require root rights should go to /usr/sbin like cangw,
> isotptun, slcan_attach, slcand
I don't feel qualified to judge that. The File Heirarchy Standard says
(http://www.pathname.com/fhs/pub/fhs-2.3.html#PURPOSE16):

	Utilities used for system administration (and other root-only
	commands) are stored in /sbin, /usr/sbin, and /usr/local/sbin.
	/sbin contains binaries essential for booting, restoring,
	recovering, and/or repairing the system in addition to the
	binaries in /bin.


> Or should they stay in /usr/bin and lead to an error when the admin rights are
> not granted??
Even if they are in /usr/sbin they should lead to an error in that case.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2013-08-18 20:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-17 19:28 [PATCH can-utils] Don't overwrite PREFIX and DESTDIR when provided via the environment Uwe Kleine-König
2013-08-17 19:32 ` Marc Kleine-Budde
2013-08-18 11:02   ` Oliver Hartkopp
2013-08-18 20:49     ` Uwe Kleine-König [this message]
2013-08-18 21:36       ` Marc Kleine-Budde
2013-08-19  8:24         ` Marc Kleine-Budde
2013-08-19  8:37         ` Uwe Kleine-König
2013-08-19 17:23           ` Oliver Hartkopp
2013-08-19 19:16             ` Marc Kleine-Budde
2013-08-20  5:29               ` Oliver Hartkopp
2013-08-20  6:55                 ` Marc Kleine-Budde

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=20130818204930.GM30496@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=socketcan@hartkopp.net \
    /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).