[Buildroot] How to provide one default skeleton per init system?

[Jérôme Pouiller]

Hello,

On Tuesday 10 June 2014 11:50:04 Thomas Petazzoni wrote:
> Dear Maxime Hadjinlian,
> 
> On Tue, 10 Jun 2014 09:21:39 +0200, Maxime Hadjinlian wrote:
> > > But if a new package target-skeleton is added, what would be the
> > > dependency
> > > chain? Would `make target-skeleton-rebuild` rebuild... the whole rootfs?
> > 
> > Actually the package that I have introduced after discussing it with
> > Thomas Petazzoni was a package called initscripts and busybox/systemv
> > only depends on it. This way, when you chose an init system, it will
> > copy the files to the target directory.
> > 
> > This seems to be less intrusive as the end users would not even notice
> > (except the disappearance of the init.d folder when systemd is
> > chosen).
> > 
> > If you have any comments regarding this idea, they are welcomed.
> > I'll try and send this patch tonight so we can discuss on the idea
> > with some code.
> 
> After thinking more about it, I believe it would be even better to have
> the whole skeleton as a package. This way, everything installed to
> $(TARGET_DIR) comes from a package, and things like my "graph-size"
> script do not need to special case the skeleton.

Hmm... This patch seems to be something close to that:
  http://patchwork.ozlabs.org/patch/335963/

I may rework it, if needed.


-- 
Jérôme Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr