From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Alexander GQ Gerasiov <gq@debian.org>
Cc: Yegor Yefremov <yegorslists@googlemail.com>,
Oliver Hartkopp <socketcan@hartkopp.net>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Nikita <nebaruzdin@lvk.cs.msu.su>
Subject: Re: can-utils: install in /usr/bin instead of /usr/local/bin ??
Date: Thu, 23 Jan 2014 21:32:58 +0100 [thread overview]
Message-ID: <52E17C7A.5070209@pengutronix.de> (raw)
In-Reply-To: <20140123202612.3ab46825@snail>
[-- Attachment #1: Type: text/plain, Size: 2131 bytes --]
On 01/23/2014 05:26 PM, Alexander GQ Gerasiov wrote:
> Thu, 23 Jan 2014 15:12:07 +0100
> Marc Kleine-Budde <mkl@pengutronix.de> wrote:
>
>> On 01/23/2014 03:07 PM, Yegor Yefremov wrote:
>>> On Thu, Jan 23, 2014 at 3:00 PM, Marc Kleine-Budde
>>> <mkl@pengutronix.de> wrote:
>>>> On 01/23/2014 02:58 PM, Oliver Hartkopp wrote:
>>>>> Hi Marc,
>>>>>
>>>>> when can-utils are now intended to be packaged for Debian:
>>>>>
>>>>> Does it make sense to move the installation directory to /usr/bin
>>>>> instead of the current /usr/local/bin target??
>>>>
>>>> No, Uwe will probably use ./configure --prefix=/usr
>>>
>>> CC Alexander and Nikita.
>>
>> I consider the plain Makefile legacy, so using autotools for the
>> debian package is the way to go. The standard way to configure the
>> installation prefix is: ./configure --prefix=/usr
>
> Well... I seen some strange behavior when tried to use autohell
What kind of strange behaviour?
> So I use plain Makefile in my not-yet-uploaded-into-Debian package.
>
> If you want to get rid of it, I'd recommend you remove it completely
> from git, rename auto* to common name (for now Makefile called
> GNUmakefile or something like that) and remove from git any
> autogenerated files.
From the GNU make info page:
""By default, when `make' looks for the makefile, it tries the following
names, in order: `GNUmakefile', `makefile' and `Makefile'.""
So GNUmakefile has a higher priority as Makefile.
There aren't any auto generated files in the git.
> So can I do auto*/configure/make, than make distclean and there will
> be no *changed* files (if there are any *new* files - it's Ok).
Just call:
./autogen.sh
./configure
make
Should work out of the box.
> Otherwise package maintainers have some headache in writing correct
> build scripts.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 242 bytes --]
next prev parent reply other threads:[~2014-01-23 20:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 13:58 can-utils: install in /usr/bin instead of /usr/local/bin ?? Oliver Hartkopp
2014-01-23 14:00 ` Marc Kleine-Budde
2014-01-23 14:07 ` Yegor Yefremov
2014-01-23 14:12 ` Marc Kleine-Budde
2014-01-23 16:26 ` Alexander GQ Gerasiov
2014-01-23 20:32 ` Marc Kleine-Budde [this message]
2014-01-23 21:46 ` Alexander GQ Gerasiov
2014-01-23 21:49 ` 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=52E17C7A.5070209@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=gq@debian.org \
--cc=linux-can@vger.kernel.org \
--cc=nebaruzdin@lvk.cs.msu.su \
--cc=socketcan@hartkopp.net \
--cc=yegorslists@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox