Sebastien Lelong wrote:
>>> These bee packages are also here to encourage integration to
>>> TORELEASE, including dependencies, as soon as possible. So once
>>> you're done on an isssue/task, update TORELEASE (and CHANGELOG) so
>>> it's included in next bee packages !
> This is a test to check if TORELEASE is consistent. For instance, last
> release showed there were missing files, dependencies, in TORELEASE. Bee
> will automatically detect this.
Already for some time I use here a script that also does some 'sanity'
check and produces some statistics. I just exhanced it today with some
checks (hence my update!). For example it checks:
- if filespecs are all lowercase
- if files are sorted alphabetically (to ease visual searching)
- if every released blink sample has a corresponding released device
file.
- if every released device file there is also a released blink sample.
I suppose Bee does something similar?
> Thinking again about this, maybe you'd like to have bee package for all
> devices ? (jallib-all_devices). Let me know.
I don't think this is very useful. Libraries and device files are not
completely independent. So better keep these distributed together.
Regards, Rob.
--
Rob Hamerling, Vianen, NL (http://www.robh.nl/)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en
-~----------~----~----~----~------~----~------~--~---
