[no subject]

[Andy Guy <awpguy@acs.ucalgary.ca>]

>
>Bruce Perens writes:
>> 
>>  boot-floppies-1.1.0-2.tar.gz source 48161 2a686d3f2c4c740faed890c1e3c9c228
>>  boot-floppies-1.1.0-2.deb misc 96362 fcc90d61c6cba533f9ac2c61e47857b9
>
>Is this a/the new dchanges format?  If so, could I as archive maintainer
>beg for something more easily scannable?  I liked the old format, but
>if it is desired to have all this info on one line, then:
>
>fcc90d61c6cba533f9ac2c61e47857b9 misc 96362 boot-floppies-1.1.0-2.deb
>

Shouldn't it be one of:

fcc90d61c6cba533f9ac2c61e47857b9 misc 96362 boot-floppies-1.1.0-2.deb
2a686d3f2c4c740faed890c1e3c9c228 misc 48161 boot-floppies-1.1.0-2.tar.gz

fcc90d61c6cba533f9ac2c61e47857b9 binary/misc 96362 boot-floppies-1.1.0-2.deb
2a686d3f2c4c740faed890c1e3c9c228 source/misc 48161 boot-floppies-1.1.0-2.tar.gz

fcc90d61c6cba533f9ac2c61e47857b9 unstable/binary/misc 96362 boot-floppies-1.1.0-2.deb
2a686d3f2c4c740faed890c1e3c9c228 unstable/source/misc 48161 boot-floppies-1.1.0-2.tar.gz

??
A script could figure where files go given the correct section to put
them in,  so just having a field

Section: misc

would do, but this dosn't allow developers to put things in the
stable/unstable directory.  Or deal with source packages that produce
binary packages that go in different directorys [do/will any].

Andy.