31.03.2015 01:08, Erich Titl пишет: > Am 30.03.2015 um 23:24 schrieb Andrew: >> 30.03.2015 23:40, Erich Titl пишет: >>> Am 30.03.2015 um 18:39 schrieb Andrew: >>>> 30.03.2015 18:23, Erich Titl пишет: >>>>> Am 30.03.2015 um 17:03 schrieb Andrew: >>> ... > ... >>>> modules.tgz updating possibility? >>> No problem on my side, recreating the tarball is a piece of cake. >> Right. Except spent time on slow PCs (but I think that really slow ones >> like Geode/i486SLC clones like Advantech one will not require modules on >> storage). >> From other side, we may store both packed and unpacked modules. > We can store packed and unpacked modules on the server. On the target > machine this is no option, at least not on all of them. There is simply > not enough storage on small media and these exist. I have one sitting in > front of me. > > .. Yes, I mean server-side storage. >> In that way all will be done in one repo, in one branch. I'm not sure >> that separate packages branch per each LEAF branch is better than >> pushing all into master branch and separating versions by tags. >> Advantage of 'all in one branch' storage - anybody can find/grab all >> current releases in one click. > That is true, it requires two clicks. > > It is not true though that you can find all releases easily right now, > and to tell you the truth, I was not even aware of a packages repository > until a few days ago and I am using LEAF for more than ten years.
> We should only have master and a few recent branches anyway. To keep the > old cruft may be fun for an archologist, not really for me. > > I don't want to keep branches, for me they are just a tool. If you can > arrange a tree structure which meets the current needs or which one can > easily adapt to, right... I don't really care. But tags fits requirements better than branches :) Branch is good for something that will change in future. Also, IMHO for each minor release we shouldn't update all packages that weren't actually changed and just rebuilded. This blows up repo without real need. IMHO we should find a way to detect 'changed' and 'unchanged' packages (for ex., first criteria - version/release, second - files list, third - required libs...). ------------------------------------------------------------------------------ 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
