From scott.jackson at enthought.com Mon Jul 16 22:14:22 2007 From: scott.jackson at enthought.com (Scott Jackson) Date: Mon, 16 Jul 2007 14:14:22 -0500 Subject: [Pisi] Subversion repositories in pspec.xml? Message-ID: <1184613262.11093.3.camel@stubbs> Hi again, As I mentioned earlier, we're trying to use pisi to power our build system, and I'm working on a way to automate nightly builds, and there's a couple things I'm trying to get past: 1) Is there a way to specify a subversion repository instead of an archive in the pspec.xml file? Right now we're passing a dummy archive in the element, and using pisi.actionsapi.subversion to check out packages from within actions.py 2) Furthermore, is there a way to specify a revision in either pspec.xml or the command line? If not, would the project appreciate a way to do this? I almost think that subversion support in pisi, if it doesn't already exist, would be integral to our efforts here, so if there's nothing already, I smell a patch brewing... :) Thanks! Jackson -- Scott Jackson Enthought, Inc. From turkay.eren at gmail.com Mon Jul 16 22:51:30 2007 From: turkay.eren at gmail.com (Eren =?ISO-8859-9?B?VPxya2F5?=) Date: Mon, 16 Jul 2007 22:51:30 +0300 Subject: [Pisi] Subversion repositories in pspec.xml? In-Reply-To: <1184613262.11093.3.camel@stubbs> References: <1184613262.11093.3.camel@stubbs> Message-ID: <20070716225130.089690f4.turkay.eren@gmail.com> On Mon, 16 Jul 2007 14:14:22 -0500 Scott Jackson wrote: > 1) Is there a way to specify a subversion repository instead of an > archive in the pspec.xml file? Right now we're passing a dummy archive > in the element, and using pisi.actionsapi.subversion to > check out packages from within actions.py I don't think that making an svn fetcher class is hard. Of course you can make a fetcher easily, it's python :) (btw, I'm not a pisi hacker, I just mentioned my idea) > 2) Furthermore, is there a way to specify a revision in either > pspec.xml or the command line? If not, would the project appreciate a > way to do this? You can write a revision like; 0.0_456734 Regards, Eren From scott.jackson at enthought.com Mon Jul 16 23:21:14 2007 From: scott.jackson at enthought.com (Scott Jackson) Date: Mon, 16 Jul 2007 15:21:14 -0500 Subject: [Pisi] Subversion repositories in pspec.xml? In-Reply-To: <20070716225130.089690f4.turkay.eren@gmail.com> References: <1184613262.11093.3.camel@stubbs> <20070716225130.089690f4.turkay.eren@gmail.com> Message-ID: <1184617274.12521.8.camel@stubbs> On Mon, 2007-07-16 at 22:51 +0300, Eren Türkay wrote: > I don't think that making an svn fetcher class is hard. Of course you > can make a fetcher easily, it's python :) (btw, I'm not a pisi hacker, > I just mentioned my idea) > Oh, I'm sure. I was just seeing if I was going to reinvent the wheel by doing that- like I said, we're passing dummy packages through right now, and if we could just place a repository in lieu of an archive, that might actually be a good bit more straightforward. I didn't know if this had been done yet. I suppose I should delve into the source, but I was seeing if anyone knew it better than I. > > 2) Furthermore, is there a way to specify a revision in either > > pspec.xml or the command line? If not, would the project appreciate a > > way to do this? > > You can write a revision like; > > 0.0_456734 > That's attractive, although I think what we might want is something more like $ pisi-cli build package/pspec.xml --revision 5342 or some such. Within pisi, we'd want it to first look for the subversion repository in pspec and then grab either the latest revision (if not specified) or the revision specified on the command line. The reason we want this, is because it greatly simplifies building nightlies and stable releases. Or *better*, would be the behavior: check for repository, if true: check for revision in commandline, if none: check for revision in pspec, if none: revision = latest What I think I've noticed, is that the "pisi way" seems to be to make separate recipes for each version. I'm considering that as an option, but I'm also leaning towards the ability to specify a stable svn tag inside pspec, and override it to build nightlies when we need to. -- Scott Jackson Enthought, Inc.