HI Erich; Am Mittwoch, 11. März 2015, 19:27:00 schrieb Erich Titl: > Am 11.03.2015 um 15:54 schrieb kp kirchdoerfer: > > Hi Erich; > > .. > > > It is part of the release work to put the files into the git repositories > > (package/5_1 etc), and it's me who does the work currently. > > > > All archs and packages are rebuild from scratch for a new release, then > > the > > tarballs will be build and a limited test with qemu is done. > > I then upload the tarballs via scp to SF FRS and the builded packages are > > committed into git repo. > > > >> There is access to the packages on SF, I found that in the meantime. > >> Unfortunately it does not really reflect the version as distributed, as > >> 5_1 is in reality 5.1.3. This is easy to understand for a human being, > >> as we know how to guess. A program or script is bad at guessing. > > > > Yes it was my decision to name it that way, because it was handy and > > worked > > for me. It can be changed as needed - but it should be smaller and we > > should have an additional repository "stable" for your upgrade script. > > I don't think so, stable should just be a link to the last stable > release, not a duplicate. This link is easy to adapt.
Tried to find info about using symlinking git repos but nothing usable so far. So I thought about another idea which doesn't need to bother you. Instead of having multiple repos (5.0,5.1, stable) we can just have two (stable and latest aka beta). The latest head in stable is the latest stable version, the remaining can be done with tagging. As I said not really important for you if you just want to download the latest stable version for upgrade. > >> There is no kernel, modules, firmware nor initrd/mod available on SF, > >> just stuffed in tarballs or iso images. We shoud make that selectable > >> too. > > > > initrd, initmod and moddb are available, kernel should be added as well as > > the firmware. Note that the flavours are part of the filename > > (*-i686,-*-geode), but I hope your script can deal with that one. > > Should be possible, needs testing. > > > And if you like, a file .version could be maintained in the stable repo. > > version is unused as of now, it helps to find what 'stable' is. It might > be interesting in the future do decide on incompatibilities > > We also need > > - an unpacked modules tarball with a list file to get module names > quickly, mine is called modules.list > - an unpacked firmware tarball > > This way we can avoid to download the huge tarballs. If we have to > unpack these on our target systems, there might not be enough space. I know, but I disagree. While I see the pro, I'd like to avoid cluttering the SF space and I'd like to keep the release work as simple as possible. Pls let's start with a basic thing - if really required it can be improved. > I suggest to ask around the users what they are using as installation > and boot media. > > > so the stable repo could look like > > > > stable/.version > > stable/i386/*.lrp (plus kernel-i686, kernel-geode etc) > > kernel-i386 no need for kernel-geode here > > + modules > + firmware > > > stable/x86_64/*.lrp ... > > stable/rpi/... > > There may be another aproach though > > stable -> 5.1.3 > latest -> 5.1.4beta > > kernel independent stuff > 5.1.3/*.lrp (no initmod, no initrd) > 5.1.3/firmware > > kernel dependent stuff > 5.1.3/i486/(linux initrd initmod) > 5.1.3/i486/modules + modules.list > 5.1.3/geode/(linux initrd initmod) > 5.1.3/geode/modules + modules.list > > 5.1.4beta..... I'd like to keep it as much as possible inline with the build environment - therefor I prefer the approach I proposed. > > You can it access with https as described in other mails. > > Sure, I will install wget-ssl and see if it performs alike on http to > see the compatibility. Pls test also http - it may work according to SF docs. 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
