On Thu, Sep 22, 2011 at 4:22 PM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote: > On Thu, Sep 22, 2011 at 10:42:31AM +0200, Jerome Martin wrote: >> Andy, >> >> On Thu, Sep 22, 2011 at 6:58 AM, Andy Grover <agrover@xxxxxxxxxx> wrote: >> > Hi Jerome, >> > [...] >> > Sounds good, but please see: >> > >> > http://fedoraproject.org/wiki/Packaging:SourceURL >> > >> > Basically, RPM assumes an upstream download URL. If this is possible for >> > you to provide then it would make life a little easier. >> >> I'll see what I can arrange. > > The idea is that every project should do somewhat frequent (depending on > the development pace) releases, and do tarballs for that. Pretty much > every software project I know works that way, and it really helps > packagers or anyone else consuming it. For example for the xfs > userspace we have a script that does all the releasing in one go: > > - update the documentation with the release date > - tag the git tree > - build the tarball > > Here's the script: Thanks for the example. The interesting point though is unclear to me in the case of your script: what happens with the tarball once generated ? I think this is what you ultimately mean: having release tarballs available from a know FTP or HTTP location. I said I would make arrangements for this, and I will. I already have several build farm / upload scripts for our internal trees following the tagging of versions in the git tree, so I am familiar with the process. I just need to decide on the best place to host this (some persistent location), whether under the www.linux-iscsi.org or www.risingidesystems.com websites hierarchies or someplace else. It is not just about targetadmin though, and I need to sync with Nic to have a common location for all our GPL-released stuff. Best Regards, -- Jérôme Martin -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
