Am Samstag, den 04.10.2008, 14:03 +0200 schrieb Adrien:
> 2008/10/2, Gerd Stolpmann <[EMAIL PROTECTED]>:
> >
> > Am Montag, den 29.09.2008, 13:04 +0200 schrieb Adrien:
> >> Hi,
> >>
> >> I'd like to make a distribution package of godi, with fast everything
> >> from lablgtk to ocisgen. The problem I'm facing is : how not to
> >> pollute the build environment ?
> >>
> >> Currently I can ./configure godi with a fake prefix. Then I would
> >> search-replace all occurences of the fake prefix (which means grepping
> >> about 400MB of hopefully cached data). It works but it's also quite
> >> ugly. Is there a better way to do that ?
> >
> > I would even say that it does not work. There are binaries and libraries
> > with compiled-in paths. You cannot easily replace them.
>
> OK, noted.
>
> >> I currently don't think there's a better solution though because the
> >> scripts can contain anything. Take the 'lablgtk' or 'lablgl' scripts
> >> for instance : they contain the prefix in a hard-coded form.
> >
> > I'm not sure that I understand what you try to do. Can you please
> > elaborate a bit more how you want to distribute godi? Why do you want to
> > change the prefix afterward?
>
> I'm working on my livecd project. Or rather scripts that automate the
> creation of livecds (if you don't have scripts, you'll necessarily
> forget something).
> Currently I managed to prepare everything (new kernel, kernel modules,
> additional applications, ...) without touching (polluting/modifying)
> the installed system. Only godi remains.
> What I wanted to do is compile godi in $TMP/$PREFIX and have it in
> $PREFIX in the final system. I'll probably add a check that $PREFIX
> does not exist on the system used to build the livecd and build
> rirectly in $PREFIX (I personnaly build in /ocaml, not something like
> /usr).
I see, the build system is not identical to the system where you to have
it finally installed.
You could also consider building in a chroot environment - this way you
have full control of the file system the build sees. You could do it
like
mkdir myroot
# make that myroot/escape can be used to get out of the chroot
mkdir myroot/escape
mount -o bind / myroot/escape
# create environment for build
ln -s ../escape/etc myroot/etc
... # long list of commands needed here to make all files available
# needed for the build
# Jump into the chroot
chroot myroot
# Now build GODI
That way you don't modify the build system globally and can nevertheless
build almost everywhere.
Gerd
>
> >> Btw, I'd like to make several smaller packages. Especially, I'd like
> >> to move the source files in a different package. I currently put
> >> everything under $PREFIX/build in a different package. Again, is there
> >> a better approach ?
> >
> > GODI comes with packages, so you could take the file lists of the GODI
> > packages.
> >
>
> Right, it will certainly need a lot more refinement.
> Thanks.
>
> ---
>
> Adrien Nader
>
>
> > Gerd
> > --
> > ------------------------------------------------------------
> > Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany
> > [EMAIL PROTECTED] http://www.gerd-stolpmann.de
> > Phone: +49-6151-153855 Fax: +49-6151-997714
> > ------------------------------------------------------------
> >
> >
> >
>
> _______________________________________________
> Godi-list mailing list
> [email protected]
> https://godirepo.camlcity.org/mailman/listinfo/godi-list
>
--
------------------------------------------------------------
Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany
[EMAIL PROTECTED] http://www.gerd-stolpmann.de
Phone: +49-6151-153855 Fax: +49-6151-997714
------------------------------------------------------------
_______________________________________________
Godi-list mailing list
[email protected]
https://godirepo.camlcity.org/mailman/listinfo/godi-list
