[baker-baker] unpacked source packages

[Mika Pesu]

T. Onoma wrote:

>Okay so I started making a recipe for Ruby 1.8.1 preview 2, which I've called 
>Ruby--1.8.1p2. The source package file is ruby-1.8.1-preview2.tar.gz, but 
>when it unpacks it creates a directory called ruby-1.8.1. Obviously this 
>would clash with preview 0, 1, etc. as well as final. Should I care about 
>that and thus have source downloads go into further subdirs based on version 
>number, i.e. /Ruby/1.8.1p2/ ? Also, there's no way for Baker to know what the 
>unpacked directory will be called, I had assumed it would be the same as the 
>source file name w/o the .tar.gz stuff, but appearently that was a bad 
>assumption. I guess I have no choice but to add another field to recipes: 
>unpacked_dirname or something like that.
>
>Any thoughts?
>
>  
>
hmm,when unpacking source code it doesnt shouldn't matter what will be 
unpacked directory called,
as long as make install creates proper directory layout in install for 
example:/usr/lib/ruby/1..8.1 etc...

i made some experiments with chrooted install by
making fake_root lets call /var/tmp/fake_root
mounting real root with read only to /var/tmp/fake_root/real_root
and chrooting to /var/tmp/fake_root
/var/tmp/fake_root should contain programs /bin/bash /lib/.... to chroot 
to propely work.

and setting path inside chroot
taking snapshot of tree structure(not taking real_root)
then compiling,installing
and taking snapshot
and when we compare these we know what files changed....

so far no luck but i'll experiment more....