From: Jamie Lenehan <lenehan@twibble.org>
To: openembedded-devel@lists.openembedded.org
Subject: sanitize.py
Date: Mon, 11 Sep 2006 09:49:00 +1000 [thread overview]
Message-ID: <20060910234900.GA25953@twibble.org> (raw)
Nice work on sanitize.py, I like it!
Here's a few things I'd like to see changed:
* For initscripts the order should be:
INITSCRIPT_PACKAGES
INITSCRIPT_NAME
INITSCRIPT_PARAMS
since the PACKAGES lists which packages we are going to have
initscripts for while the NAME and PARAMS are repeated for each one
of those packages, like this:
# Main init script starts all deamons
# Seperate init script for watchquagga
INITSCRIPT_PACKAGES = "${PN} ${PN}-watchquagga"
INITSCRIPT_NAME_${PN} = "quagga"
INITSCRIPT_PARAMS_${PN} = "defaults 15 85"
INITSCRIPT_NAME_${PN}-watchquagga = "watchquagga"
INITSCRIPT_PARAMS_${PN}-watchquagga = "defaults 90 10"
Also it seems to split these up when they probably should be kept
together. ie, the above currently comes out as this:
INITSCRIPT_NAME_${PN} = "quagga"
INITSCRIPT_NAME_${PN}-watchquagga = "watchquagga"
# Main init script starts all deamons
# Seperate init script for watchquagga
INITSCRIPT_PACKAGES = "${PN} ${PN}-watchquagga"
INITSCRIPT_PARAMS_${PN} = "defaults 15 85"
INITSCRIPT_PARAMS_${PN}-watchquagga = "defaults 90 10"
* For alternatives the order should be:
ALTERNATIVE_NAME
ALTERNATIVE_PATH
ALTERNATIVE_LINK
ALTERNATIVE_PRIORITY
since NAME and PATH are required while LINK and PRIORITY are
optional. I think it's better to always have the two required entries
first and then the optional ones, like this:
ALTERNATIVE_NAME = "awk"
ALTERNATIVE_PATH = "gawk"
ALTERNATIVE_LINK = "${bindir}/awk"
ALTERNATIVE_PRIORITY = "100"
It also splits these up and they should probably be kept together as
well. ie, the above currently comes out as this:
ALTERNATIVE_LINK = "${bindir}/awk"
ALTERNATIVE_NAME = "awk"
ALTERNATIVE_PATH = "gawk"
ALTERNATIVE_PRIORITY = "100"
* It doesn't know about the PKG variable (the name of the package,
used to prevent debian.bbclass from changing the name to an
internal shared library name.):
## Warning: unknown variable/routine "PKG_${PN}-ospfd = ${PN}-ospfd"
## Warning: unknown variable/routine "PKG_${PN}-ospfclient = ${PN}-ospfclient"
* It doesn't know about pre/post rm/install scripts (maybe it's not
meant to?):
## Warning: unknown variable/routine "pkg_prerm_${PN} () {"
## Warning: unknown variable/routine " ${sysconfdir}/init.d/quagga stop"
## Warning: unknown variable/routine "}"
## Warning: unknown variable/routine "pkg_prerm_${PN}-ospfd () {"
## Warning: unknown variable/routine " ${sysconfdir}/init.d/quagga stop ospfd"
## Warning: unknown variable/routine "}"
--
Jamie Lenehan <lenehan@twibble.org>
next reply other threads:[~2006-09-10 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 23:49 Jamie Lenehan [this message]
2006-09-11 4:10 ` sanitize.py cyril Romain
2006-09-11 22:09 ` sanitize.py cyril Romain
2006-09-11 22:19 ` sanitize.py cyril Romain
2006-09-11 23:51 ` sanitize.py Jamie Lenehan
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=20060910234900.GA25953@twibble.org \
--to=lenehan@twibble.org \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.