Checksums.ini sorting and updating

Checksums.ini sorting and updating

[Koen Kooi]

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

Re: Checksums.ini sorting and updating

[Otavio Salvador]

Hello,

On Sun, Nov 8, 2009 at 7:36 AM, Koen Kooi <k.kooi@student.utwente.nl> wrote:
> 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 :)

While I agree that we shouldn't remove recipes just for fun I also
believe we ought to ignore overlays out there since if they wait to
use a stable codebase, there's a stable branch available for it.
Another thing is that I disagree about keeping it growing. IMO
checksums.ini ought to reflect what is in current metadata and not
all versions that has existed on it.

If someone uses it in a overlay he/she can keep a specific
checksums.ini for it as well.

-- 
Otavio Salvador                  O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854         http://projetos.ossystems.com.br

Re: Checksums.ini sorting and updating

[Otavio Salvador]

On Sun, Nov 8, 2009 at 7:36 AM, Koen Kooi <k.kooi@student.utwente.nl> wrote:
> 2) people having deleted(!) checksums that repear due to being in my TMPDIR
> checksum cache

I pick the specific checksum I'm going to add and add it to
conf/checksums.ini (copy it from TMPDIR/checksums.ini) so I avoid
adding non-related checksums (as you did in the tarball change) for no
reason.

-- 
Otavio Salvador                  O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854         http://projetos.ossystems.com.br