[M3devel] CM3_INSTALL_PREFIX

[Jay]

I made this change years ago but only recently did Olaf switch over to my stuff. It is a good change generally, because you don't have to run cminstall and stick a full path in the config file. We can fix this aspect of it, but I'd like to be able to see it fail before I fix it, and then verify my fix makes it stop failing.
 
 
 - Jay




----------------------------------------
> From: dragisha at m3w.org
> To: jay.krell at cornell.edu
> Date: Fri, 5 Jun 2009 01:13:19 +0200
> CC: m3devel at elegosoft.com
> Subject: Re: [M3devel] CM3_INSTALL_PREFIX
>
> There is no problem in CM3_INSTALL_PREFIX, but in situations where
> make_dir tries to make ".bin/.." when "..bin/" still does not exist.
>
> Problem is recent, it started to happen after you make INSTALL_ROOT
> relative to cm3 binary location.
>
> Solution: Exterminate .. from paths in cm3cfg.common.
>
> Apropos CM3_INSTALL_PREFIX - I am maybe it's only "client" for now - as
> it's used to populate tree during RPM builds. But it's straightforward
> solution to any binary packaking problem.
>
> On Thu, 2009-06-04 at 19:42 +0000, Jay wrote:
>> Dragisha,
>>
>> ok, even before looking into this, I think I knew what the problem is.
>> Need to "smush out the dots" more, so that mkdir /a/b/c/d/.. acts like
>> mkdir /a/b/c.
>>
>> However I am unable to reproduce the problem on either PPC_DARWIN or
>> AMD64_LINUX.
>>
>> Can you show me the offending .M3SHIP files?
>> And maybe your config files?
>>
>> I don't have any .. "like that" in .M3SHIP.
>>
>> Does it happen with current cm3 or only older cm3?
>> (I didn't realize CM3_INSTALL_PREFIX was a relatively new thing, from
>> early 2008.)
>>
>> - Jay
>>
> --
> Dragiša Durić 
>