Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] [RFC PATCH 0/1] Generating package skeletons
@ 2015-09-28  7:46 Chris Packham
  2015-09-28  7:46 ` [Buildroot] [RFC PATCH 1/1] scripts: Add gen-package.py Chris Packham
  0 siblings, 1 reply; 5+ messages in thread
From: Chris Packham @ 2015-09-28  7:46 UTC (permalink / raw)
  To: buildroot

Hi,

Not sure if this has come up before but I figured most of the 'standard'
things for adding a package[1] can be somewhat automated, and that
automation might solve some of the minor style issues that crop up.

But just because something _can_ be automated it doesn't necessarily
follow that something _should_ be automated. By my (fairly unscientific)
count between 2015.05 and 2015.08 there were 95 new packages and between
2015.08 and master there are 36 new packages (so far). Having a script
to generate the skeleton for those packages would have saved a few
keystrokes (although I haven't checked that my script would generate
something valid for those 95/36 packages).

Is this an idea worth pursuing (adding docs, handling cases like
SITE=$(call github, ...) and git/hg repositories)?

[1] - http://buildroot.org/downloads/manual/manual.html#adding-packages

Chris Packham (1):
  scripts: Add gen-package.py

 support/scripts/gen-package.py | 266 +++++++++++++++++++++++++++++++++++++++++
 1 file changed, 266 insertions(+)
 create mode 100755 support/scripts/gen-package.py

-- 
2.5.0

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2016-03-07 23:07 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-09-28  7:46 [Buildroot] [RFC PATCH 0/1] Generating package skeletons Chris Packham
2015-09-28  7:46 ` [Buildroot] [RFC PATCH 1/1] scripts: Add gen-package.py Chris Packham
2016-03-06 22:22   ` Thomas Petazzoni
2016-03-07  7:40     ` Chris Packham
2016-03-07 23:07       ` Arnout Vandecappelle

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox