[gobolinux-users] sandboxintall broken?

kenneth marken k-marken at online.no
Fri Jun 29 21:28:37 UTC 2007


On Friday 29 June 2007 23:22:11 Jonas Karlsson wrote:
> On Fri, 29 Jun 2007 23:13:50 +0200, kenneth marken <k-marken at online.no> 
wrote:
> > On Friday 29 June 2007 23:05:17 kenneth marken wrote:
> >> On Friday 29 June 2007 22:53:37 Jonas Karlsson wrote:
> >> > On Fri, 29 Jun 2007 22:51:09 +0200, kenneth marken
> >> > <k-marken at online.no>
> >>
> >> wrote:
> >> > > On Friday 29 June 2007 22:37:51 Jonas Karlsson wrote:
> >> > >> On Fri, 29 Jun 2007 21:26:57 +0200, kenneth marken
> >> > >> <k-marken at online.no>
> >> > >
> >> > > wrote:
> >> > >> > im trying to do some manual source based installs, and it seems
> >> > >> > to work fine up until the sandboxintall stage. it keeps reporting
> >> > >> > something about orphaned files when it does the postprosessing of
> >> > >> > the sandbox.
> >> > >> >
> >> > >> > btw, im using the guide in the wiki for this.
> >> > >>
> >> > >> SandboxInstall is quite tricky to use by its own. I would recommend
> >> > >> creating a recipe for the application you're trying to build. Most
> >> > >> of the times (there are very few exceptions) you will gain more
> >> > >> time than you put into making the recipe.
> >> > >>
> >> > >> If you still want to use SandboxInstall by its own you should note
> >> > >> what files that are orphaned and either change/patch the
> >> > >> installation process to install those files into the application's
> >> > >> prefix or make the files unmanaged by passing the conflicting files
> >> > >> or directories to SandboxInstall using the '--unmanaged-files'
> >> > >> option, e.g.
> >> > >> 'SandboxInstall
> >> > >> --unmanaged-files="/System/Variable/log/foo:/System/Variable/lock/f
> >> > >>oo" foo 1.0'
> >> > >>
> >> > >> The former is prefered for most files or directories.
> >> > >
> >> > > well if thats the case, maybe the wiki should get a rewrite or
> >> > > something?
> >> >
> >> > Which page? I'll take a look at it.
> >>
> >> http://gobo.kundor.org/wiki/Manual_Compile
>
> Actually I couldn't see anything wrong with that page, except that it
> didn't mention that one should try to create a recipe first and only use
> manual compilation if everything else fails, so I've added this.
>
> >> > Secondly 'SandboxInstall -h' does print (as a note)
> >> >
> >> > "Normally you'll want to use Compile(1) instead.
> >> > 'SandboxInstall' is called by Compile(1)."
> >> >
> >> > Perhaps that should be rephrased to emphasize it?
> >>
> >> now, if Compile(1) had the option to go ahead and try to create a
> >> recipie if you aimed it at a tar-ball and it could not find one (outside
> >> of it not being able to contact any server) it would be golden. but
> >> right now i dont see it does not, at least automatically. that way one
> >> had only two commands. Compile for when one is working on source,
> >> InstallPackage when wanting to install a package.
> >
> > looked into it some more and i find that the toolkit is more buildt
> > around finding the download url, set up the place for it to live ones
> > done, and then have the system download it. while good, it would be nice
> > if it had some kind of option for when one have allready downloaded the
> > sourcecode and wants to install it from the comforts of ones home dir.
>
> Please look at the --help for each of the tools. Most of the tools support
> the '--no-fetch' option, which prevents the script to go online. So in your
> case the commands would be:
> 'MakeRecipe --no-fetch foo 1.2 http://some.bogus/or/real/url'
> 'Compile --no-fetch foo 1.2'
> If you use a real url for MakeRecipe you don't have to specify name and
> version in most cases.

would be equally nice if they could take a local file rather then a url and be 
done with it.


More information about the gobolinux-users mailing list