[baker-baker] Re: baker

[T. Onoma]

On Saturday 29 November 2003 11:24 am, Mika Pesu wrote:

> code is well organized,i'm currently seeking solutions for fake_root
> install.
>
> chrooted install:
>     i'm not sure if i have misunderstand the concept you have had in mind.
>     do we compile package like normally and use chroot just in install
> phase(not in compile phase just: make install)
>     or we use chroot in whole package build phase(./configure;make;make
> install)?

good question. if we just do install then only need to worry about the common 
system files that the program installation will want to change. if we do 
compile then we have to link all the libs it will need in the fake root so it 
can find them. it certainly would be safer, but more work for us and recipe 
maintainers i think. of course we could just copy the whole system to a sub 
directory ;-)

> about the install_indicator:
>     yeah,i gave a lot of time for this for good solution,and this is
> currently better, we dont need framework for other package managment stuff,
>     but we do need to add few more "features" for this.

true true. Version Detection!

>     i havent checked from code this:do we currently map fhs to
> install_indicators path like if i have
>     /bin/bash in install indicators does it map to fhs setted in
> configure files to check it in proper place
>     so if i have /bin/ mapped to /foo/bar/bin does it check
> /foo/bar/bin/bash to see if it installed?

it dosen't do it yet, but that's the idea.

>     we should probably need somekind of search util, little desc about
> this: if i compile foo_lib to /opt/shells/foo/1.1/lib and i want to compile
> program with baker that depends on foo_lib
>     and user has setted his enviroment so that it normally compiles fine
> but baker looks install_indicators /lib/foo_lib1.*
>     and doesnt find it so it starts to re-build foo_lib to /lib.
>     so what i suggest is that we add just filename(s) to
> install_indicator and search it through fs and we add
>     additional  install directory indicator to config files where user
> can add own paths
>
> for example if i have install_indicator_dirs in config like this
> /bin
> /sbin
> /Programs/*/bin
> /opt/own/libs/
>
> and i have install_indicators in recipe file
> ['lib1','foobin']
>
> so it does search on /bin/lib1,/bin/foobin,/sbin/lib1,/sbin//foobin,and
> so on....
>
> any thoughts?

actually it already does something like this. in install indicators you can 
put:

     - /usr */lib1 share

the spaces indicate the the first part is the root dir to search, the second 
is the "grep" to search for, and the last means prune/don't seach this sub 
dir. It should work (i may have commented out in code), but it is SLOWWWWWW! 
if we can speed it up A LOT then that would be fine. on the other hand, 
perhaps it would be better just to have an install_indicator_script ? that 
way you can do anything you need to. although that's less safe.

-t0