Re: [gentoo-dev] automate "make install" stuff

[Marius Mauch]

On 06/17/04  pclouds wrote:

> Hi,
> I have an idea of using something like checkinstall/sandbox to
> automate src_install phase without making patch for it.
> Here it is:
> we do "make install" in chrooted env.
> There is nothing in chrooted env, so it won't work. The
> idea is to make chrooted env as same as the real env. We preload a lib
> to monitor file access before chrooting. The lib is much like
> sandbox/installwatch. When it encounters a file access, it will make a
> link from the original file to DESTDIR so that programs running inside
> chrooted env can see it.

Why the chroot and linking stuff? This will get extremely annoying. How
about programs the Makefile has to run (cp, make, install, chmod, ...).

> Another problem is when programs modify/delete a file out of chrooted
> env. In this case, it will fail. It should be handled by hand. The lib
> should ignore (or make it as it's done. the original files don't
> change actually).
>
> The last problem is that links will not be deleted over time. They may
> grow if some programs scan the whole tree such as find. Most
> install scripts won't afaik.

Well, that's the smallest problem.

> Ok, once "make install" is done, we have DESTDIR with all installed
> files and some links. Some works are needed to remove links.
>
> Don't know if it's usable, so post it here :) Any suggestions?
>
> PS. I don't mean to replace src_install. It's  for quick, dirty
> ebuilds. It's  for guys that want to install/test some programs
> quickly.

I don't get what problem you're trying to fix in the first place. Whats
wrong with the current sandbox that would be fixed by your suggestion?

Marius

-- 
Public Key at http://www.genone.de/info/gpg-key.pub

In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.