Hi KP Am 12.03.2015 um 17:59 schrieb kp kirchdoerfer: ...
> > It seems one of us has a misconception of the SF features we can use. > > It is my understanding that we only have limited access/space to/on the SF > shell, and it's mainly used to install a CMS, but not to use it as space to > maintain directories and files like on a ftp server. > I found no traces of such a thing in teh SF documentation. OK, be it that way, but if you upload files, do you have any control on the location, e.g. the URL they can be accessed with? > > So IMHO we do have only the option to use git repos and FRS to make files > available from SF. > FRS will not fit our needs, so using git repos is a workaround. At least it > offers the git server feature to access files via http (wget). > > Anyone may correct me if I'm wrong. I'd be happy cause I'm not that keen > about > using git for that purpose as it seems :) > ... >> >> ... >> >>> 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. >> This _is_ the basic thing. It is _necessary_ because there is >> insufficient space on embedded devices. The only other option I see is a >> web process, which can be fed with kernel module names and builds moddb >> on the fly for the target machine. You don't want to embed this in upgrade. >> >> ... >> >>>> 5.1.4beta..... >>> >>> I'd like to keep it as much as possible inline with the build environment >>> - .... >> >> It is almost a perfect match, does not have 5_1 though :-) >> and has kernel, initrd modules anf firmware (and version and modules lists). > > Look for > > https://sourceforge.net/p/leaf/packages/ci/master/tree/stable/ > > does that help you? It might but IMHO it is overkill. Like I stated in one of my last mails, a version file holding the release would be enough to point upgrade to the correct content. e.g. https://sourceforge.net/p/leaf/packages/ci/master/tree/stable/version > > In fact it's 5.1.4-rc1 ( kernel update), but that's what we can do using SF > fetaures. If that doesn't fit, we have to think once again of moving stuff > away > from SF to ?? - to start with, why is there i386 and not something covered by $ARCH, e.g. i486, geode, i686? - there is no version file, so you need to populate the whole tree, does not bother me but possibly SF 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
