All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Checksums.ini sorting and updating
Date: Sun, 08 Nov 2009 10:36:09 +0100	[thread overview]
Message-ID: <hd63e9$t75$1@ger.gmane.org> (raw)

Hi,

When adding a new recipe I do:

cd $TMPDIR
cat /OE/org.openembedded.dev/conf/checksums.ini >> checksums.ini  ; 
python 
/OE/org.openembedded.dev/contrib/source-checker/oe-checksums-sorter.py 
checksums.ini > /OE/org.openembedded.dev/conf/checksums.ini

Then, when possible, I match the new entries in conf/checksums.ini to 
the sums upstream publishes. After that I will try to build the recipe 
and if successfull commit it.

Sometimes I encounter what look like spurious changes in 'git diff 
conf/checksums.ini' which are caused by:

1) pre-coffee manual additions that are in the wrong place and get resorted
2) people having deleted(!) checksums that repear due to being in my 
TMPDIR checksum cache

Now 1) can be solved by running a script like the one I mentioned above, 
but 2) needs an attitude adjustment. OE is not wikipedia where recipes 
get deleted because a single person thinks no-one is using them. We have 
lots of people using external overlays for various recipes and deleting 
things from checksums.ini will only make their life harder.

So, please stop deleting checksums and start using a more automated way 
to update checksums.ini :)

regards,

Koen




             reply	other threads:[~2009-11-08  9:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-08  9:36 Koen Kooi [this message]
2009-11-08 13:31 ` Checksums.ini sorting and updating Otavio Salvador
2009-11-08 13:35 ` Otavio Salvador

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='hd63e9$t75$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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.