[gobolinux-users] sandboxintall broken?

[kenneth marken]

On Saturday 30 June 2007 02:15:14 Michael Homer wrote:
> On 6/30/07, Isaac Dupree <isaacdupree at charter.net> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > kenneth marken wrote:
> > > as in, its clear that the tools are made for contributors rather
> > > then end users.
> >
> > although, it's very nice that because the tools ask a little extra out
> > of you, every end user can very easily become a contributor!  It is one
> > of the outstanding things of GoboLinux versus other packaging systems.
> > Also (for more than one-off things, which almost anything has the
> > potential to become) it makes it easier to repeat compiling(/installing)
> > what you already have.  I find that relaxing.
> >
> > That being said, yes, the tools are not optimized for things that don't
> > have a Uniform Resource Identifier (URL).  ...if you store stuff in a
> > consistent place on your system, how about a file:///x/y/z url, does
> > that make any sense? We really don't want people to get lazy and use the
> > stuff they've already downloaded, it is way too tempting and makes it
> > harder(read: non-trivial, so it is very likely not to happen at all) to
> > submit working-anywhere(in theory), verified recipes.
>
> You can just put it in /F/C/Archives and specify the filesize and md5.
> It won't even try to download it, so you could use a nonce URL, or do
> something useful and provide a real one. It's not a huge effort to do.
> Extracted sources can go in /F/C/Sources in much the same way, but
> you'll have to say yes, you want to use the existing directory (and
> it's more of a hack).
>
> I see no motivation to make that easier. If you deliberately choose
> not to contribute and that makes your life harder, I really don't
> care. So long as it's possible to get things done, and it's easy to
> get them done the right way, I'm pretty pleased with it.
>

noted, and i may well provide some recipes or packages after i get my head 
around the details of the process. right now its the issue of what to do with 
orphaned files after a compile. beyond that i think im starting to get the 
hang of it. hmm, maybe ill do a first draft of how its done on the wiki if 
noone else have done so while i was gone.