From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-06-08
Date: Thu, 12 Jun 2014 09:08:22 +0200 [thread overview]
Message-ID: <20140612090822.1e5a9e58@free-electrons.com> (raw)
In-Reply-To: <20140611215425.GD27579@free.fr>
Dear Yann E. MORIN,
On Wed, 11 Jun 2014 23:54:25 +0200, Yann E. MORIN wrote:
> > Should it be provided by the systemd package or should we create a new one?
> > Are there other packages that require such wrappers?
>
> I think if we go that route, we should just bundle it in Buildroot, and
> always install it.
>
> After all, all this wrapper does is look for --relative in the
> arguments, and if found, emulates it; otherwise, it just calls to the
> real ln.
>
> Sounds reasonable to me (although I did not look too closely if the
> script was entirely correct.)
>
> But I'd like input from Thomas and Peter on that one.
Well, I'm not sure I want to include a wrapper that will wrap *all* ln
calls, just for the sake of fixing one package. I probably prefer to
patch that package only.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-06-12 7:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-06-08 Thomas Petazzoni
2014-06-09 10:07 ` Yann E. MORIN
2014-06-09 10:11 ` Thomas Petazzoni
2014-06-09 10:15 ` Yann E. MORIN
2014-06-09 12:04 ` François Perrad
2014-06-09 12:19 ` Yann E. MORIN
2014-06-09 21:10 ` Eric Le Bihan
2014-06-11 8:56 ` Thomas Petazzoni
2014-06-11 21:04 ` Eric Le Bihan
2014-06-11 21:13 ` Yann E. MORIN
2014-06-11 21:47 ` Eric Le Bihan
2014-06-11 21:54 ` Yann E. MORIN
2014-06-12 7:08 ` Thomas Petazzoni [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=20140612090822.1e5a9e58@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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