On Fri, Jun 15, 2007 at 02:25:25PM +0200, silverdr@inet.com.pl wrote: > Thus - making the rpm or deb target install into /usr (even if I am > not fan of it unless the package becomes part of the global > distribution) does not disturb that own builds from the sources may > still install into /usr/local. In some cases I'd even say that it > properly complements. The reason for installing in /usr/local is to distinguish "local" files from "official" ones. With the availability of package management systems like rpm or deb, this distinction is no longer necessary: The package manager can always tell, which package a file belongs to and who built the package. Dependencies make sure that a packages cannot be installed if the necessary prerequisites aren't matched. Instead of installing into /usr/local, my suggestion is therefore to build and install packages. This is in fact what I do with foreign software. I don't know about .deb files, but building RPMs is rather easy, and it enables me to remove ALL files that are part of an application suite, even after a year or so, when I have forgotten about it. Regarding the default setting in the master makefile: I'm not using it to build the RPM packages. So I can live easily with /usr/local as default if this is the wish of the majority. On the other side, changing a line in the makefile or calling make with "prefix=/usr/local" on the command line is not what I would call a real effort, so I don't see it as a big issue. Regards Uz -- Ullrich von Bassewitz uz@musoftware.de ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Fri Jun 15 18:34:19 2007
This archive was generated by hypermail 2.1.8 : 2007-06-15 18:34:22 CEST