Re: [cc65] building under cygwin

On 2007-06-15, at 18:34, Ullrich von Bassewitz wrote:

>
> 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:

Yes and no. Please take the general example that I gave in the  
previous post.

> 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.

If someone wants it that way - sure! But... we are talking about RPM  
now. How about PKG, DEB, SIS, INST and, and...? Thus, unless someone  
does all the work to allow easy building of packages for all the  
supported systems - building binaries from sources is much more  
"safe" option. BTW. I usually do my builds into "local" also because  
overwriting something at the "global" level is easy, while returning  
to the earlier stage in such case is much more difficult.

> 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.

Again - take the generic example I gave in the previous post. There  
are cases where it is much safer or even desired to keep the "local"  
version separate.

> 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.

It's not a big issue but... once I occasionally forget about doing  
it, because practically all other builds install into local - I end  
up with a situation, which is clearly bad. Manual cleaning (and being  
sure that nothing gets omitted/overwritten/deleted) is an additional,  
unnecessary and error prone work.

And last but not least that manual change requires (at least required  
not that long ago) also adding CC65_INC=/usr/local/lib/cc65/include  
CC65_LIB=/usr/local/lib/cc65/lib to the envars. Another thing that is  
quite uncommon and easily gets forgotten. Then, only after digging up  
the reasons for something not working, it comes back to mind.

Please don't get me wrong - we are talking about actually a minor  
change that IMHO makes the situation much more comfortable for (I  
presume) most people willing to build from sources, while not doing  
any harm to people willing to install from RPM.

1. default "prefix" to be /usr/local
2. taking care of the LIB and INC paths at the Makefile/build level

With best regards.

----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.