Hi Erich; Am Montag, 2. März 2015, 00:52:15 schrieb Erich Titl: > Am 01.03.2015 um 16:52 schrieb kp kirchdoerfer: > > Hi Erich; > > .. > > >> What exactly is different from the sourceforge pages? > > > > The Packages 5.x page is available. > > For whatever reason we can't this page to SF, it will not have the > > expected > > content, whereas the page on zetam.org does. > > ... > > > I see the page and I can imagine how to get the content. > > The Packages page on zetam provides links to the git repository for > > Packiages, you can either download by clicking the Package or fetch the > > Package with wget with the link shown > > > > wget > > https://sourceforge.net/p/leaf/packages/ci/786d2c9d66decc4c2d8409362f1180d > > 9446f0271/tree/5_1/i386/accel.lrp?format=raw (on one line of course) > > Sure, and it might be possible to rearrange the links, so they would be > more simple. For example the GIT hash does not help here at all.
It's the download link. No need to rearrange and it's avoided cause it will break... > my current definitions for the kernel, for example > > LEAFURL=http://leaf.think.ch/stable > > ARCH=`uname -r | sed s/^.*-//` > KERNEL=`find $MOUNTPOINT -name linux 2> /dev/null` > LINUX=$LEAFURL/$ARCH/syslinux/linux > > So you see deceivingly simple. Indeed. I can't compare - currently the kernel is not part of the donwload page... > > This way we don't need the packages anywhere in the SF Files Area and > > still > > can maintaining with git. > > > > A pro for the page mentioned is that we have: > > a) a showcase of available packages > > b) reuse all the information given in buildtool.cfg - including > > dependencies, package verson and revision > > That is fine, I don't doubt this, just that parsing all this information > is not easy. I don't want to have a requirement of a parsing language. Ok. > > How do you fetch your packages from leaf.think.ch? > > And how can we make shure to work with dependencies with a flat repo as > > leaf.think.ch? > > I don't, because I don't need to. Upgrade does just this, upgrade. It > takes the information of a currently working system and tries its best > to lift it to an actual version. What is Ok, I understand, that you are thinking about full-distro-upgrade and don't bother with packages updates. Even the first one would be a nice improvement. > > Just to be clear - I don't want to push neither git nor the packages page, > > just looking for a working solution, which will not raise maintenance > > work. > > Oh, the current page is deceivingly dumb. It is just an unpacked tarball > and it is only necessary because the tarball would be too big and would > require too much processing to run it to the target system. It is so > much faster to fetch a file from a file system than unpacking it from an > archive. I think it won't be possible to fetch from a tarball - for most of the devices it won't be possible to keep even tarball in RAM not to mention the unpacked one. So if you don't want to deal with dependencies, revision, incremental updates etc, there is one remaining pb- I'm not aware of any place in the net, where we can store the unpacked tarballs other than a git repo - either SF, github, or...., at least not without putting more responsibilty to an individual maintaning our own server. We do have two choices: Searching for a file area (you may even ask on SF if that is possible (we currently use GB's of disk space... and I'm afraid they won't be too happy)) - or you may rethink your decision not to deal with a git repo. Maybe we do have a third option I forgot... kp ------------------------------------------------------------------------------ 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
