30.03.2015 18:23, Erich Titl пишет: > Am 30.03.2015 um 17:03 schrieb Andrew: >> 30.03.2015 17:21, Erich Titl пишет: > ... > >>> Impossible, it is too big. Upgrade is not thought as an initial setup tool. >> But this will cause a mismatched modules.tgz version. And will cause a >> headache for adding new hardware that isn't supported by currently >> loaded modules. > There is no modules.tgz on the target machine, therefore no modules.tgz > version neither. > > Correct, you cannot just add hardware without adding modules. As there > is no space on the target machine to hold modules.tgz this is not > relevant. Lots of our systems are single board computers and there is > not that much hardware to be added. With the new set up you can fetch > individual modules from sourceforge, which you could not in the past. And lots of systems aren't hardware-limited, so maybe we should leave modules.tgz updating possibility? > > ... >>> have a way improving the dependencies, be my guest. >> Nope, we have deps into /lib/modules/<kernel>/modules.dep. And we have a >> script that searches for dependencies for list of modules (currently >> it's used for generating moddb/initmod from module list). > Those deps files are build at machine boot, not before. > > ... Those deps are also built on build system. You can find modules.dep in staging/<arch>/lib/modules/<target> dir. >>>> Why we can't use git tags for this? >>> Maybe we can use git tags. I have not tested this. branches are more >>> convenient at development stage. >> We may ad tags x.x-stable and x.x-development. > If you can show me the functionality, be my guest. Tag points to commit. It can be accessed by web like git branch or commit (https://sourceforge.net/p/leaf/packages/ci/<tag>/tree/).You can check it on source repo: https://sourceforge.net/p/leaf/bering-uclibc/ci/5.0.1-beta1/tree/
Currently we push packages, for ex., to 5_0 and 5_1 (and in future to 5_2) dirs, and for each 'stable' release (for ex., 5.1.3) we haven't sub-releases that may be done later than next 'development' release (for ex., we didn't provide 5.1.3.1 after 5.1.4-rc1). So we need just add/update tags '5.1-stable' and '5.1-development' at each commit (if we committed 'stable' release - add '5.1-stable' and '5.1-development' tag to this commit ensure that 'development' users uses most recent version; if we committed 'development' release - just add/update '5.1-development' tag). And of course also add tags with releases (like in source repo). So, if we will have tags in repo, to access to right version of packages we should use https://sourceforge.net/p/leaf/packages/ci/5.1-stable/tree/5_1/ as base URL (5.1-stable commit in 5_1). Or even for manual downgrade due to regression - something like https://sourceforge.net/p/leaf/packages/ci/5.1.1/tree/5_1/ > >> Or we can use symlinks that points to right place. > Difficult unless we use Yves' git store module, which I failed to > understand. Why? Git symlik should be accessed like regular dir from the web. > >> File with path IMHO a bad idea. > Currently there are only file paths, have a look at the master branch in > the packages repository. My branches are cleaner IMHO. > > cheers > > ET > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > > > _______________________________________________ > leaf-devel mailing list > leaf-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/leaf-devel ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
