On Apr 13, 2007, at 1:02 PM, Randal L. Schwartz wrote:
No, because the CPAN.pm shell is an installer, not a packager. It
does not
maintain a list of which files belong to which installations, and
will happily
let two installations both write to the same file. This will be
problematic
whe
(Randal L. Schwartz) schrieb:
> If CPANPLUS offers uninstall, it lies about it. The same limitations
> apply.
CPANPLUS also knows about that and explicitely warns you, that if you
installed via a packager, this packager should also be used to uninstall.
If the user still wants CPANPLUS to unin
yitzle wrote:
OK... I got this script that gets a lot of hits -> generates high
bandwidth.
Is there a simple way to check the amount of bytes printed to STDOUT so I
can track the bandwidth it is generating?
You may be able to get this information from your web server log files?
If you're usin
> "Andreas" == Andreas Puerzer <[EMAIL PROTECTED]> writes:
Andreas> If the user still wants CPANPLUS to uninstall, it uses the .packlist to
Andreas> unlink the files in the distribution (that's what i would do if i were
Andreas> to remove a module by hand).
Andreas> That is an Uninstall, the
> "Xavier" == Xavier Noria <[EMAIL PROTECTED]> writes:
Xavier> Wouldn't the problem with file name collisions/rewrites potentially
Xavier> happen if packages were managed as in distros?
The problem is that there's no promise that package A and B from the CPAN
don't both install file C. So an
I will test the tell function out.
I don't think I got access to the server log files.
On 4/14/07, Nigel Peck <[EMAIL PROTECTED]> wrote:
yitzle wrote:
> OK... I got this script that gets a lot of hits -> generates high
> bandwidth.
> Is there a simple way to check the amount of bytes printed to
Hi,
Thanks for the reply, I think that I understand you point.
Now I am starting to fear cpan installations.
Is there a chance that by doing a simple - naive cpan installation of a module
I, potentially, can damage another installed module?
Best regards,
Yaron Kahanovitch
- Original Me
