<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
The ".." gets smushed out early for me and I don't see a failure.<BR>
Even for shipping m3core into a nonexistant place, with CM3_INSTALL_PREFIX set.<BR>
Is the problem without CM3_INSTALL_PREFIX?<BR>
Can you show your .M3SHIP files?<BR>
And maybe your config files?<BR>
This is easy to fix. There is code that smushes out dots.<BR>
It is maybe a problem to write the quake because quake is very limited in what it can do.<BR>
There might be functions now that can do it though.<BR>
But really, again, the Modula-3 code often "canonicalizes" paths internally anyway, which is possibly why I don't see the problem occuring myself.<BR>
<BR>
- Jay<BR><BR> <BR>> From: dragisha@m3w.org<BR>> To: jay.krell@cornell.edu<BR>> Date: Fri, 5 Jun 2009 10:51:05 +0200<BR>> CC: m3devel@elegosoft.com<BR>> Subject: Re: [M3devel] CM3_INSTALL_PREFIX<BR>> <BR>> This is special case, as CM3_INSTALL_PREFIX redirects installation<BR>> process to empty tree... cm3 -ship fails on<BR>> make_dir("/usr/local/cm3/bin/../lib") as there is no<BR>> $CM3_INSTALL_PREFIX/usr/local/cm3/bin at that moment. "cm3 -ship" which<BR>> fails does mkdir $CM3_INSTALL_PREFIX/usr/local/cm3/bin, though. So<BR>> second time I start cm3 -ship it works fine.<BR>> <BR>> Also, if I "mkdir -p $CM3_INSTALL_PREFIX/usr/local/cm3/bin" before cm3<BR>> -ship it does not fail first time.<BR>> <BR>> Thus said - I already have fix I need, it's workaround but works. If it<BR>> is problem for you to write wuake script which derives paths from<BR>> INSTALL_ROOT without ".." then just forget this and we can document this<BR>> "feature" on our way. It will be documented in my RPM recipes once I<BR>> complete and publish them.<BR>> <BR>> On Thu, 2009-06-04 at 23:21 +0000, Jay wrote:<BR>> > <BR>> > I made this change years ago but only recently did Olaf switch over to<BR>> > my stuff. It is a good change generally, because you don't have to run<BR>> > cminstall and stick a full path in the config file. We can fix this<BR>> > aspect of it, but I'd like to be able to see it fail before I fix it,<BR>> > and then verify my fix makes it stop failing.<BR>> > <BR>> > <BR>> > - Jay<BR>> -- <BR>> Dragiša Durić <dragisha@m3w.org><BR>> <BR></body>
</html>