Am 04.03.2015 um 15:29 schrieb kp kirchdoerfer: > Am Dienstag, 3. März 2015, 22:49:19 schrieb Erich Titl: >> Am 03.03.2015 um 17:09 schrieb kp kirchdoerfer: >>> Erich; >>> >>> will something like that in a file help you? >>> ... > > As Andrew noted it can be dropped, will do so. > >> 5_1 --> preferably mapped to stable | latest or whatever static value. > > Don't know if we can work with symlinks in a git repo...
Depends on what a git repo really is. The way I understand it it is only an aggregation of files with a number of hidden directories with control info. As there is a cgi interface used to fetch the files something probably adds the 5_1 to the path. Git by itself cannot decide about version numbers. so it must have been defined at setup. > ... > > Yes my fault when setting up the git repo. > >> Is https a requirement at sourceforge? > > No, if it's a pb, I can change to http It just requires wget-ssl. IMHO we should drop the non-ssl wget as it is just a subset of wget-ssl. > >> What about the kernel and init[rd|mod] > > initrd is there, initmod is there as flavours (-geode, -i486,-i686...) That is fine, I just have i486 installed on my server for the test. If we ever support non x86 architectures we would probably need to investigate into initrd too. > >> How can we build a initrd.single (for boot loaders that do not support >> multiple initrd files) > > I run > cat initrd.lrp initmod-rpi.lrp > initrd-rpi.lrp > for a raspberry pi, seems to work. Interesting, both files are compressed separately. What do you use as a bootloader? > > I suggest you have look into the Packages repository and try to rearrange so > it will fit your needs and I'll try to create one or flat files out of it. Actually all I need is a defined access to the files. In my test case I just use the unpacked tarball. The selection of stable or latest is completely random. I would love if we could use DNS records to get the URL of such a location, but I have not found a tool in LEAF which allows to fetch ressource records other than MX or A... > > I have no objection if we don't care about the Release number (5.1) and use > "stable" "beta" "next" instead, but pls keep in mind the idea was also to > have > a Packages page where users can download fixed packages between releases. That _must_ not be affected. I don't know what kind of access we have to sourceforge's servers. I just know the RCS access and have not looked further. E.g. > we could have offered a fixed package for bash a few hours after shell-shock > fixes has arrived for 5.1 and 5.0 via a proper packages page. This worked for > 3.0, but then the SF broke (I guess too much stuff for phpwebsite or whatever > CMS we use on SF). Yves and myself started to fix that recently... > So any rearrangement should fit your needs for a full upgrade and the idea to > provide fixes between releases. Based on the full upgrade it should not be very difficult to write a package based upgrade. The problem is interoperability and compatibility. cheers ET
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
