[Beaker-devel] Tool for Inventory gathering

Nick Coghlan ncoghlan at redhat.com
Wed Jul 10 05:38:54 UTC 2013


On 07/10/2013 03:11 PM, Amit Saha wrote:
> Valid points, Nick. If I understand correctly, this is what you are proposing:
> 
> - Patch lshw as and when needed and submit those patches upstream. When and whether
> at all they get into lshw is lyonel's call.
>  
> - However, create and maintain a beaker-lshw package which will be rebuilt whenever we 
> have a substantial patch to server our immediate goals and will be the one we depend on
> for our needs.
> 
> Did I get that right?

Short term, yes. Longer term, we may want to talk to Lyonel about
helping directly with lshw maintenance - if we can do lshw releases
whenever we get hold of a new piece of gear it doesn't handle correctly,
then the need for beaker-lshw could go away entirely.

This may turn out to be a one time thing, though - we're picking up a
whole lot of details at once due to our own migration from smolt, so it
may be we'll be able to drop our custom patches with the next upstream
release and reduce beaker-lshw to a spec file and a symlink.

Cheers,
Nick.

-- 
Nick Coghlan
Red Hat Infrastructure Engineering & Development, Brisbane

Testing Solutions Team Lead
Beaker Development Lead (http://beaker-project.org/)


More information about the Beaker-devel mailing list