Re: objection! [was Re: Icon and pixmap location]

1999-11-17 Thread Branden Robinson
On Tue, Nov 16, 1999 at 03:00:30PM +, Julian Gilbey wrote: If you don't intend for it to be used as an icon, don't put it there. Meanwhile, /usr/{something}/pixmaps could reasonably be interpreted as a respository for all sorts of .xpm's, regardless of their purpose. A thought on this

Processed: Fixed in NMU debian-policy 3.1.1.0

1999-11-17 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: severity 49901 fixed Bug#49901: Correction to the build-dependency spec, Packaging manual section 8.1 Severity set to `fixed'. quit Stopping processing here. Please contact me if you need assistance. Darren Benham (administrator, Debian Bugs

Bug#48045: debian-policy: non-US is a misnomer

1999-11-17 Thread Joel Klecker
At 14:42 + 1999-11-16, Philip Hands wrote: libmagick4g-lzw If you look at the license, it's DFSG, so the only reason it's in non-free is because of the Unisys patent. [Scott, that's right isn't it?] This is wrong AFAICS. Yes, wrong and codified in policy, see Bug #46522. I don't think

Re: objection! [was Re: Icon and pixmap location]

1999-11-17 Thread Joey Hess
Branden Robinson wrote: When they say monochrome, they mean .xbm's. Why not just have a /usr/share/image directory in which images of any format or size can be placed? It sure would make things simpler. Just allow subdirectories in it, please. I have about 3 thousand .xpm and .xbm files on

Re: objection! [was Re: Icon and pixmap location]

1999-11-17 Thread Branden Robinson
On Wed, Nov 17, 1999 at 12:14:05AM -0800, Joey Hess wrote: Branden Robinson wrote: When they say monochrome, they mean .xbm's. Why not just have a /usr/share/image directory in which images of any format or size can be placed? It sure would make things simpler. Just allow

Bug#49901: marked as done (Correction to the build-dependency spec, Packaging manual section 8.1)

1999-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 1999 03:20:57 + with message-id [EMAIL PROTECTED] and subject line Closed with policy 3.1.1.0 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your