From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package: Fix overwrite inittab w/ default skeleton
Date: Fri, 17 Jul 2015 00:56:58 +0200 [thread overview]
Message-ID: <55A836BA.8050905@mind.be> (raw)
In-Reply-To: <CAGduivwRsW1SPqnNuncicLy5geAL72PZtfdbMydr5qncG_4DTg@mail.gmail.com>
On 07/16/15 23:42, Maxime Hadjinlian wrote:
>
> On Jul 16, 2015 11:35 PM, "Thomas Petazzoni"
> <thomas.petazzoni@free-electrons.com
> <mailto:thomas.petazzoni@free-electrons.com>> wrote:
[snip]
>> I agree with you that this is a change in behavior, but I would say
>> it's a change for good: making people realize that using a custom
>> skeleton very often doesn't work as they intend it to work.
>>
>> Any opinions from others?
> I agree that a custom skeleton is not the proper way to go and leads to more
> errors and trouble than anything.
> I would remove the possibility entirely.
I have one use case that still needs a custom skeleton (i.e. I found no other
way to handle it). There's a system where I want /bin to symlink to /usr/bin, to
avoid some problems with wrong absolute paths in scripts. Turns out that doing
that in a post-build script doesn't work because some other symlinks get broken,
so it needs to be done in the skeleton...
Now, Peter wasn't against changing the default skeleton to do exactly that,
because it also solves the issue when busybox installs something in /bin while
the full version installs it in /usr/bin. So in that case, yes we could probably
eliminate the custom skeleton. Though there may be other cases.
Regards,
Arnout
> I can cook up a patch at that effect.
> It would greatly disturb many user though. It needs to be well thought through.
>>
>> Thanks!
>>
>> Thomas
>> --
>> Thomas Petazzoni, CTO, Free Electrons
>> Embedded Linux, Kernel and Android engineering
>> http://free-electrons.com
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-07-16 22:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 16:30 [Buildroot] [PATCH] package: Fix overwrite inittab w/ default skeleton Maxime Hadjinlian
2015-07-16 16:38 ` Gustavo Zacarias
2015-07-16 21:07 ` Thomas Petazzoni
2015-07-16 21:17 ` Gustavo Zacarias
2015-07-16 21:35 ` Thomas Petazzoni
2015-07-16 21:42 ` Maxime Hadjinlian
2015-07-16 22:56 ` Arnout Vandecappelle [this message]
2015-07-16 21:48 ` Gustavo Zacarias
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=55A836BA.8050905@mind.be \
--to=arnout@mind.be \
--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