Re^2: What's the best way to avoid name collisions when creating files?

Replies are listed 'Best First'.
Re^3: What's the best way to avoid name collisions when creating files? by philiph (Acolyte) on May 03, 2005 at 13:36 UTC
Although Data::UUID looks like an interesting solution, one big annoyance for me is it doesn't come standard in my Perl distribution (Fedora Core 1).	[reply]
Re^4: What's the best way to avoid name collisions when creating files? by adamk (Chaplain) on May 03, 2005 at 15:16 UTC
Unfortunately, RedHat is not the most pregressive distribution in the world. In fact, _most_ distributions contain only a pitiful amount of the CPAN modules that exist. There are 8000 CPAN packages. That is more than some distributions. PAUSE see updates for up to 50 packages a day. That is more than some distributions. Because of the sheer volume of packages, CPAN is to some degree a victim of it's own success. If a module isn't used by an application that has 100,000 users, its unlikely to end up being packaged simply because it would be unrealistic for distros to do them all. They'd simply swamp the package management system. In fact, I'd go so far as to say you arn't a "real" Perl programmer until you exceed the boundaries of the modules that are available on most distros.	[reply]
Re^5: What's the best way to avoid name collisions when creating files? by philiph (Acolyte) on May 03, 2005 at 15:42 UTC
Certainly it's possible for me to use packages that don't come with the system. It's just difficult. This isn't just a home computer, it's part of a production network at a financial company. I first have to test the package on a spare system. Then I have to get approval from my boss. Then I have to schedule the install for off hours and perform it. Basically unless a CPAN module provides clearly necessary functionality, I'm going to try to avoid installing it. Thus while the UUID approach is interesting, I don't see enough in it to justify the work of getting that CPAN module installed, as opposed to trying other alternatives. For example, calculating md5 sums on the messages is much easier because that module comes with the Fedora perl installation.	[reply]
Re^4: What's the best way to avoid name collisions when creating files? by dragonchild (Archbishop) on May 03, 2005 at 13:49 UTC
`$ perl -MCPAN -e 'install Data::UUID'` [download] should do the trick. Don't be stupid and refuse to use the 7000+ distributions that don't come standard with Perl. The Perfect is the Enemy of the Good.	[reply] [d/l]
Re^5: What's the best way to avoid name collisions when creating files? by halley (Prior) on May 03, 2005 at 15:59 UTC
Mixing CPAN installations with an RPM-managed system can be a pain in the rear. However, a quick google search found several `perl-Data-UUID-*.rpm` files available, so it's just a matter of installing it. If it wasn't already available, it's pretty easy to make a .src.rpm of most CPAN tarballs. Then rebuild the .rpm and install those on whatever machine farm you manage. -- `[ e d @ h a l l e y . c c ]`	[reply] [d/l]