Re: Fwd: [leaf:packages] New commit by kapeka

Hello Erich;

Am Sonntag, 27. September 2015, 13:55:34 schrieb Erich Titl:
> Hi KP
> I checked the contents of the 5_2 directory this morning using
> build_upgrade
> 
> running build_upgrade with parameters 5.2.x 5_2

while this is fine for testing, we'll need more work for a comprehensive 
solution within the build process.
As I said before, some of the packages are committed from packages directory, 
the kernel from build dir and some finally from the images. This requires a lot 
of manual intervention and should be improved.
Ideas welcome.

> 
> I checked as far as I could, now starting to build the upgrade branch
> Gewechselt zu einem neuen Branch '5.2.x'
> delete 3_1
> delete 4_0
> delete 4_3
> delete 5_0
> delete 5_1
> skip 5_2 it is in the delete_mask
> delete latest
> delete stable
> delete stable-test
> skip tools it is in the delete_mask
> 
> If you continue here the changes made by build_upgrade will be committed
> to branch 5.2.x.
> Do you wish to continue? Y/N (N)
> 
> It appears that no missing files were detected. However build_upgrade
> does not handle firmware yet and thus master is not yet ready to be
> tagged. I will extend build_upgrade to include handling of the firmware
> tarball too.
> 
> Andrew incuded modules.sqfs to be unpacked and used at system boot, but
> how is the firmware tarball to be used? I am not sure the firmware
> tarball is used anywhere but in the upgrade tool. Here the use of a
> squash file system would be reasonable too.

Currently the firmware.tgz needs user intervention.
One can unpack firmware and copy required files to /lib/firmware and then they'll 
saved with lrcfg... 
To support more automagic integration AFAIK we need either to enhance modules 
or to come up with a new config file. Or something else.
 
> Also I believe we can remove the stable-test directory and, to be
> honest, I am not sure we need to conserve 3_1 and 4_0.

stabble-test has been what it says - a branch you've created for testing.

I agree we don't need 3_1 and 4_0 any longer, but IMHO it doesn't hurt to keep 
as-is.

kp

------------------------------------------------------------------------------