Once upon a time, Chip Turner <cturner@xxxxxxxxxx> said: > Ville Skyttä <ville.skytta@xxxxxx> writes: > > The modules come from a vendor -> they should go into vendor install > > dirs. Site install dirs are for local site installs so that admins can > > override system installed stuff a la "perl -MCPAN -e install Foo-Bar" > > and traditional tarball install. (Moving site_perl in /usr/local/... > > would make this clearer FHS-wise.) > > I like that idea. A lot. I'd not thought about it til now, but that > makes a tremendous amount of sense. It would also address the manpage > issue, I think. It would break backwards compatibility, though, with > older RPMs (unless we still looked in the /usr/lib/.../site_perl/ > dirs, but I'm inclined not to). Hmm, you might as well change "vendor_perl" to "rpm_perl" then. I don't want RPM touching /usr/local (that's for the few odds and ends I install manually and local or per-system scripts), but I install perl modules from RPMs all the time. "vendor" to me means Red Hat or Fedora, so I wouldn't make my perl module RPMs install into the "vendor" directory. -- Chris Adams <cmadams@xxxxxxxxxx> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble.
