[Buildroot] Startup files numbering policy

["Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>]

Dear Thomas Petazzoni,

On Tuesday, May 21, 2013 11:24:48 PM, Thomas Petazzoni wrote:
> Dear Beno?t Th?baudeau,
> 
> On Tue, 21 May 2013 23:10:40 +0200 (CEST), Beno?t Th?baudeau wrote:
> 
> > I don't have the exact use case in mind, but I have encountered this issue
> > at
> > least once on a project with many startup scripts. The board needed many
> > custom
> > startup scripts in its target skeleton, and in the end there was a
> > collision
> > with BuildRoot's predefined startup script numbers that broke the expected
> > startup order. It was also unclear how to number the board-specific startup
> > scripts before launching the 1st build, and without a list there is always
> > the
> > risk of a collision when enabling a new package.
> 
> Ok.
> 
> > I don't think that changing the current script numbering would be a
> > solution,
> > because that could cause an issue for someone else. There could perhaps be
> > a
> > document listing the numbering of the startup scripts installed by all
> > BuildRoot
> > packages. That would make it clear how to assign a new startup script
> > number,
> > what to expect from BuildRoot, and how to perform custom adjustments (i.e.
> > post-build script).
> 
> Isn't:
> 
> $ find package/ -name 'S[0-9][0-9]*'
> 
> a good enough documentation for this?

Maybe. This is what I had done. I mostly wanted to know if you would add a
mechanism for that, which you answered. E.g., PTXdist has a config option with a
default value giving the file name to use for each startup script.

Best regards,
Beno?t