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. > >> 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 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..... > > 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. ... > > While you should have shell access, you don't need it IMHO. I haven't used it > for years. Well, I prefer to see things as they are not as presented by some file manager. I have been able to get shell access, but not to the packages directory. 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
