Re: plans for discover transition (was: plans for d-i string freeze) [progeny.com #2385]
On Mon, Dec 08, 2003 at 12:08:02AM +0100, Gaudenz Steinlin wrote:
> We are aware of that and did some tests with it. I tried to build the
> state of the repository as it was on the day the public access was
> announced, but it failed. After a quick glance over the build system I
> noticed, that it changed quite a lot. Without the build failure the
> resulting udeb should be quite good now. (eg. built without curl)
> There should be one open ticket for the build system of discover-data in
> your trouble ticket system. I did not notice any progress on this since
> 11/18. [progeny.com #2385]
Progeny's ticket #2385 doesn't talk about build issues:
Subject: Discover 2: reduce size of discover udeb
http://lists.debian.org/debian-boot/2003/debian-boot-200310/msg00042.html
Makefile:
- only include needed devicetypes (instead of excluding uneeded ones)
- do not install old hwlist in udeb
- compress udeb hwlists
debian/control
- add build dependency on python-xml
debian/rules
- do not include docs in udeb
reduce-xml:
- remove entries with kernel module "unknown" or "ignore"
If you have better python-xml skills, you will probably
find a better way to adress this node in the xml-tree.
There's also a M$-Excel File in the source tar file
(merged_vendor_list.xls). AFAIK debian policy does not allow proprietary
data formats in source files.
As noted elsewhere on the discover-workers list, almost all of the above
is done. The exceptions are the reduce-xml issue, which I've sent a
separate mail about, and the .xls file -- I don't feel removal is
warranted because this .xls file works fine with the version of Gnumeric
in Debian testing. Consequently, I do not feel that the file qualifies
as being in a "proprietary data format" per Debian Policy. If you
disagree, please make a case for your position. :)
--
Branden Robinson | GPG signed/encrypted mail welcome
branden@progeny.com | 1024D/9C0BCBFB
Progeny Linux Systems | D5F6 D4C9 E25B 3D37 068C
| 72E8 0F42 191A 9C0B CBFB
Reply to: