Hi. 02.04.2015 11:22, Erich Titl пишет: > Hi Folks > > Upgrade has proven to be functional on the i386 platform. I cannot judge > other platforms, as I don't have any hardware to test with. > > I would like to know what you judge necessary to enable the packages > repository to serve the necessary files. As KP pointed out, existing > procedures build the packages in the current format, but I have no > indication what these procedures are. > > I would like to attack a holy cow here, the modules tarballs. I judge > them to be unnecessary. IMHO they serve no real purpose, as they need to > be unpacked in any case before the modules can be accessed and installed > by any hwdetect driven or other method. There is hardly any space saving > with these tarballs, as the modules themselves are compressed and the > tarballs need to be unpacked to find and access the modules. I know this > can be done on the fly but it is quite resource heavy. > The only reason why they still exist are file systems which either > cannot handle long filenames and/or do not care about letter cases. > I see that some packages right now have names which would not be > possible in the standard 8.3 format and so assume that the letter case > is solved too. Single tarball is easier for update than hundreds of small files. Another point of .tar.gz usage (or even just .tar - modules are compressed, so tarball compression is unnecessary) - fs cluster size. Bunch of files will use more space than single file (approx by cluster_size/2 * files_count). Even we can mount tarball via fuse or use http://avf.sourceforge.net/ > > Concerning the size of our repositories on sourceforge I would like to > start a discussion on how to differentiate the various releases of LEAF. > Right now it appears that each version consists of the whole collection > of the packages, if individual packages are changed or not. They are > just written to a directory in the repository and thus duplicated. If we > had a way to only update packages which really are different, we could > use tags or branches to differentiate releases and save quite some > space. This of course needs some versioning of individual packages and > not only LEAF releases. Versioning is already here (package version + package release) - but it isn't used in release preparing.
> 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
