Am Dienstag, 10. März 2015, 21:28:25 schrieb Erich Titl: > Hi KP > > Am 10.03.2015 um 19:48 schrieb kp kirchdoerfer: > ... > > > Don't think so, they generate the same links as proposed. > > Yes, they _generate_ it. That must be the CMS underneath.
I guess they use http://git-scm.com/docs/git-http-backend a git feature. > >>> And what's the problem to use http/s access to git repo? > >> > >> None, it just requires the ssl version of wget. > > > > Seems true, I might have been misleaded by seamless change to https in the > > browser. > > So be it. > > > >>> Again, why? > >> > >> Because if we don't know, we don't know where to put the files. I have > >> no clue what the release process needs. > >> .. > > > > As I said, go to the repository Packages and create a new directory > > "stable" and commit the files you need for an upgrade to stable. > > > > See also https://sourceforge.net/p/leaf/packages/ci/master/tree/ > > > > which is the web-interface to packages as SF offers it. > > So how do you generate packages for all the releases? Do you have a > repository per release? buildtool, buildpackages, git plus a few scripts to save typing. > > We can think about cleaning up the Packages repo and symlinks etc later, > > so it will be less than 2GB. > > In the long run, we have to take care to commit the stable packages (incl. > > kernel, and a version file if needed etc) as part of releasing a new > > stable > > version. > > I would think selecting a package as stable should just be a symlink to > correct package tree. > > >>> Agreed. I wasn't clear enough and a solution the either or the other way > >>> is > >>> easy. > >>> For wget-ssl we do have to install openssl libs (430kb) as well. > > I don't know about others, but this is on mine anyway. Rather loose some > weight on the module side. AFAIK it's not that easy to save space/memory with modules, not shure what platforms will break, if we remove some of them. But if someone investigate candidates for removal it will be nice. > >> upgrade would take care of that :-) > > > > How? :) > > Magic :-) the code reads the dependencies. > > > We have also the option to check for wget(-ssl) and libssl, and if not > > present give the advice to install it with apkg -i only for the upgrade > > process. > Ugly, what is wrong to just have wget (with ssl) . I cannot think of a > reason not to do so. I can thin of cases that they might be onyl needed for upgrading, so we may think about supporting this use-case. kp > > We need to document the stuff in the wiki anyway and for shure we also the > > blog and mailinglist to make clear what's needed, what works and what > > doesn't. > Oh sure > > >> I will extend the upgrade options to allow the selection of 'latest' or > >> any old release. > > > > Great. > > Yes, but that would require to name these releases according to the same > schema. IMHO it is not worth to do this for old stuff > > I tried to log into sourceforge, I just get thrown out. Probably not > enough privileges :-( > > cheers > > Erich ------------------------------------------------------------------------------ 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
