ing a "portupgrade -a" operation... is that
numerous of my /var/db/pkg/*/+CONTENTS files appear to have gone
walkabout, for no apparently good reason. The first manifestation
of this problem that I noticed was a series of messages of the following
general form when I ran pkg_version:
p
C, Perl, or Python.
How do you determine it is bloat and not needed by some tool? For
example the recent speed improvements for package registration grep
for the dependencies in the +CONTENTS files. The checksums are needed
for integrity checking, and the rest is needed management stuff.
por
Alexander Leidinger wrote:
Quoting Garrett Cooper <[EMAIL PROTECTED]> (from Mon, 02 Jul
2007 00:55:25 -0700):
[LoN]Kamikaze wrote:
Garrett Cooper wrote:
Pardon me for being naive, but wouldn't it be wiser for all of the
data
in the +CONTENTS file to be aggregated into sections instead of h
Quoting Garrett Cooper <[EMAIL PROTECTED]> (from Mon, 02 Jul
2007 00:55:25 -0700):
[LoN]Kamikaze wrote:
Garrett Cooper wrote:
Pardon me for being naive, but wouldn't it be wiser for all of the data
in the +CONTENTS file to be aggregated into sections instead of having
line by line info?
Ex
[LoN]Kamikaze wrote:
Garrett Cooper wrote:
Pardon me for being naive, but wouldn't it be wiser for all of the data
in the +CONTENTS file to be aggregated into sections instead of having
line by line info?
Example (net/samba_3.0.25a):
@comment MD5:9e94560ac5e757d3bc5f922dcf3ab4fb
man/man1/lo
Garrett Cooper wrote:
> Pardon me for being naive, but wouldn't it be wiser for all of the data
> in the +CONTENTS file to be aggregated into sections instead of having
> line by line info?
>
> Example (net/samba_3.0.25a):
>
> @comment MD5:9e94560ac5e757d3bc5f922dcf3ab4fb
> man/man1/log2pcap.1.gz
Pardon me for being naive, but wouldn't it be wiser for all of the data
in the +CONTENTS file to be aggregated into sections instead of having
line by line info?
Example (net/samba_3.0.25a):
@comment MD5:9e94560ac5e757d3bc5f922dcf3ab4fb
man/man1/log2pcap.1.gz
[~100 lines of repetitive data...]
