Hi KP Am 10.03.2015 um 17:27 schrieb kp kirchdoerfer: > HI Erich; > > Am Montag, 9. März 2015, 22:46:19 schrieb Erich Titl: >> Hi KP >> >> Am 09.03.2015 um 18:55 schrieb kp kirchdoerfer: >>> HI Erich; >> >> ... >> >>> Don't know about symlinks, maybe Yves can help. But thats how I'd do it; >>> clone the packages repository: >>> >>> git clone ssh://yoursfusern...@git.code.sf.net/p/leaf/packages >>> leaf-packages >>> >>> Note it's huge (approx 2GB and takes a while (we may need to think about >>> shrinking it...) > > We should investigate symlinks with git or any other idea to don't let it > grow > that fast. Maybe I will wotk with tags for versions..., but stable and latest > might be symlinks. Yves any idea? > > >>> Then follow the tips here: >>> http://bering-uclibc.zetam.org/wiki/Bering-uClibc_5.x_-_Developer_Guide_-_ >>> Hints_and_Tips_for_using_Git_SCM#Remote_Branches >> I have no problem with remote branches and I don't see a problem >> building a web tree. Now sourceforge has a scripting engine in front of >> the web access to the raw files and that is the opaque area. > > What engine do you refer to?
Well there must be some CMS magic involved to present their pages. > > And what's the problem to use http/s access to git repo? None, it just requires the ssl version of wget. > > >>>>> https://sourceforge.net/p/leaf/packages/ci/master/tree/stable/i686/packa >>>>> ge >>>>> .lrp?format=raw >>>> >>>> Mhhh... why should master be in that URL. There is no magic in neither >>>> packages, master, ci nor tree. I would like to see something like >>>> >>>> schema://sourceforge.net/?/leaf/stable >>>> >>>> If git enforces such a naming scheme it suld be easy to get raund it >>>> using symbolic links. >>> >>> Maybe, anyway it would be a start to get tests going... >> >> For testing the functionality, my simple set up is sufficient. >> We need >> in depth knowledge how sourceforge (not git) builds its web access. > > 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. .. > > 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. upgrade would take care of that :-) I will extend the upgrade options to allow the selection of 'latest' or any old release. Other > solution is to keep wget and use http link. The one that makes it, will have > to be installed by default. cheers Erich
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ 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
