Le mercredi 21 novembre 2007 à 14:08 -0500, Daniel Schepler a écrit :
Some of the common false positives are /var/lib/pkg or /etc/pkg, or
subdirectories under one of those. Since pkg often doesn't match the
binary package name exactly, I don't see any easy way to detect these cases.
What
On Thu, Nov 22, 2007 at 12:55:50PM +0100, Josselin Mouette wrote:
What I'm suggesting is to grep for them in maintainer scripts. Any empty
directory created in /etc and which isn't used in the maintainer scripts
is likely to be a mistake.
You'd need to check binaries as well - quite a few
Am Mittwoch, den 21.11.2007, 05:11 +0100 schrieb Michael Biebl:
All of my packages listed there are false positives. What I noticed
though, are a lot of packages, shipping empty /usr/sbin, /usr/bin/,
/usr/lib/ or /usr/include directories.
This directories, very likely, come from dh-make *.dirs
Hi,
Le mercredi 21 novembre 2007 à 05:20 +0100, Michael Biebl a écrit :
Imho adding a lintian check for empty /usr/bin, /usr/sbin, /usr/lib and
/usr/include directories (as created by dh-make) would be a good start.
Maybe we could check for empty directories except for a number of common
false
* Josselin Mouette [EMAIL PROTECTED] [071121 10:08]:
Maybe we could check for empty directories except for a number of common
false positives (like the python-support directories or /var/games), and
for the rest, grep in the maintainer scripts.
And menu-methods (which cause a lot of
Josselin Mouette wrote:
Maybe we could check for empty directories except for a number of common
false positives (like the python-support directories or /var/games), and
for the rest, grep in the maintainer scripts.
zope-common needs /var/lib/zope and the Zope packages come with somthing
On Wednesday 21 November 2007 04:08:44 am Josselin Mouette wrote:
Hi,
Le mercredi 21 novembre 2007 à 05:20 +0100, Michael Biebl a écrit :
Imho adding a lintian check for empty /usr/bin, /usr/sbin, /usr/lib and
/usr/include directories (as created by dh-make) would be a good start.
Maybe
On Tuesday 20 November 2007 11:20:17 pm Michael Biebl wrote:
Imho adding a lintian check for empty /usr/bin, /usr/sbin, /usr/lib and
/usr/include directories (as created by dh-make) would be a good start.
I wrote a lintian check implementing the conservative approach, and submitted
a patch as
Daniel Schepler wrote:
On Tuesday 20 November 2007 11:20:17 pm Michael Biebl wrote:
Imho adding a lintian check for empty /usr/bin, /usr/sbin, /usr/lib and
/usr/include directories (as created by dh-make) would be a good start.
I wrote a lintian check implementing the conservative approach,
Neil Williams [EMAIL PROTECTED] writes:
The only problem with the patch is that /usr/lib/perl5/ is often
included just by creating a perl package. I've tried to get rid of it
but it *is* created during 'make install' by use ExtUtils::MakeMaker;
but it is not necessarily used by package files.
I recently noticed that many of the binary packages in Debian have unnecessary
empty directories in them, so I wrote a script to find all packages with any
empty directories. The results are too numerous to post on the list. The
list by maintainer/uploader is at
http://people.debian.org
Daniel Schepler schrieb:
I recently noticed that many of the binary packages in Debian have
unnecessary
empty directories in them, so I wrote a script to find all packages with any
empty directories. The results are too numerous to post on the list. The
list by maintainer/uploader
Daniel Schepler schrieb:
On Tuesday 20 November 2007 10:26:39 pm Cyril Brulebois wrote:
On 21/11/2007, Daniel Schepler wrote:
Obviously, a lot of these will be false positives, so I definitely
won't file mass bugs based on this list without checking the full
details first.
Maybe suggesting a
.
so I wrote a script to find all packages with any
empty directories. The results are too numerous to post on the list. The
list by maintainer/uploader is at
http://people.debian.org/~schepler/empty-dirs-maint.txt
and the full list of empty directories found is at
http
Daniel Schepler wrote:
Obviously, a lot of these will be false positives, so I definitely won't file
mass bugs based on this list without checking the full details first.
Using python-support also creates false-positives. python-support relies
on having /usr/share/python-support/packagename/
15 matches
Mail list logo
