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...) > > 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. > >>> https://sourceforge.net/p/leaf/packages/ci/master/tree/stable/i686/package >>> .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. > >>> Later this should contain a stable version like 5.1.2, 5.1.3, 5.2... >>> >>> And if possible a git repo "latest" where you can fetch with >>> >>> https://sourceforge.net/p/leaf/packages/ci/master/tree/latest/i686/package >>> .lrp?format=raw >>> >>> we can use this for testing/playing and later beta versions may live >>> there. >> >> Sure, right now upgrade is geared towards 'stable', as I believe that is >> what the end user wants. > > Yes, but during testing I can the source to point to latest and to play with > that without disturbing stable. sure, right now there are just symbolic links from either stable and/or latest to the (one and only) release I copied into the web path. > >>> Note https://sourceforge.net/p/leaf/packages/ci/master/tree/stable is the >>> fixed part AFAIK, the arch and package name is no different from current >>> code, "?format=raw" needs to added to your code. >> >> Ugly, but what the hell >> For the https part, to avoid problems I suggest to drop wget.lrp and >> rename wget-ssl.lrp. The difference in size of the two packages does >> IMHO not warrant to have both. > > We don't need https, but we can also remove wget and have wget-ssl as > default. > But either way we to install a wget package with leaf or by instruction. Hmm.. to start with this, you need either a current config.lrp (or the two files upgrade and common_functions in /usr/sbin) _and_ wget*.lrp installed on your router. So any one of the wget flavours is a prerequisite. Also you need a reasonably runnig box and internet access. Just be aware, upgrade is not going to configure your box, it will just try to upgrade to a certain release level, well it may give you a smaller moddb.lrp. My motivation was to save headaches on the upgrade process. 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
