review request: firmware-tools, ubuntu/debian sponsor needed

Michael E Brown Michael_E_Brown at Dell.com
Thu May 17 23:48:49 CDT 2007


On Wed, May 16, 2007 at 04:20:41PM +0200, Martin Pitt wrote:
> 
> Right in general, but this is set up (by default) for public python
> modules. Thus the modules land in
> /usr/share/python-support/firmware-tools/, where they can be directly
> imported with e. g. 'import repository' from any python program. The
> module names are way too generic for this (repository, package, etc.).
> Also, if they are useful for other packages, public Python
> modules/packages should be shipped in a separarate binary package
> python-<module_or_package_name>.
> 
> So you should either:
> 
>  - put those modules into a python package 'firmware_tools' to get a
>    proper namespace for them.

I've elected to move everything to firmwaretools/ python package. This
involves a bit of work, though, so is ongoing.

> ==== firmware-addon-dell ====
> | +Package: firmware-addon-dell
> | +Architecture: any
> 
> There is nothing platform dependent in the package, so this should be
> 'all'.

Well, this was a major discussion point for fedora. Firmware-addon-dell
depends on libsmbios. The libsmbios package is only available/applicable
for i386, x86_64, and ia64.

If it is available in all arches it creates an incomplete dependency
tree for all other arches.

Comments? Is making this *all* still the right answer considering this?

--
Michael


More information about the firmware-tools-devel mailing list