Re: monotone-usher or usher-server and usher
Richard Levitte <[email protected]>
| Newsgroups | gmane.comp.version-control.monotone.devel |
|---|---|
| Message-ID | <[email protected]> |
In message <[email protected]> on Tue, 27 Dec 2011 02:39:56 +0000 (UTC), Hendrik Boom <[email protected]> said: hendrik> On Tue, 27 Dec 2011 01:26:42 +0000, Hendrik Boom wrote: hendrik> hendrik> > On Tue, 20 Dec 2011 10:21:19 +0100, Richard Levitte wrote: hendrik> > hendrik> >> In message <[email protected]> on Mon, 19 Dec 2011 hendrik> >> 22:09:13 +0100, Ludovic Brenta <[email protected]> said: hendrik> >> hendrik> >> ludovic> ... but TTBOMK nobody has packaged usher yet. Sorry about hendrik> >> ludovic> that. hendrik> >> hendrik> >> There's no final package distributed to Debian, but there's an effort hendrik> >> in branches org.debian.usher and org.debian.usher.experimental. hendrik> > hendrik> > So far I've been advised to look at hendrik> > org.debian.usher hendrik> > org.debian.experimental Correction: org.debian.usher.experimental hendrik> > and hendrik> > net.venge.monotone.contrib.usher Yup. Let me explain a bit how this is organized, and why you need two of those branches... (it's the same as for monotone itself) First of all, we have the main usher source, without the debian packaging stuff. It resides in net.venge.monotone.contrib.usher, and that's all that should be there. Then, we have the debian packaging stuff, which ends up in the debian/ subdirectory of the software you want to package. That directory is in its own separate branch, org.debian.usher and an experimental sibbling, org.debian.usher.experimental. At this point, you should read the policy for debian packaging: https://code.monotone.ca/p/debian-mtn/page/Policy/ (and hey Ludovic! I believe it needs being updated! ;-)) hendrik> I'm evidently still doing somethihg wrong -- again -- because after I hendrik> executing hendrik> hendrik> mtn pull "mtn://code.monotone.ca/monotone?org.debian.usher" Yup, that's not the correct server. The debian stuff is in mtn://code.monotone.ca/debian-mtn However, considering what I wrote above, that isn't enough either. A quick way to do this is: mtn clone "mtn://code.monotone.ca/contrib?net.venge.monotone.contrib.usher" usher cd usher mtn clone "mtn://code.monotone.ca/debian-mtn?org.debian.usher" debian The correct way is a little bit more complex. Since Debian packages are built from source distributions, the correct way is to build a source distribution, unpack that, clone the debian directory inside the resulting directory, then build your debian package from there (using debuild or pbuilder or whatever you fancy) hendrik> On the other hand, I have no trouble getting hendrik> net.venge.monotone.contrib.usher hendrik> which seems to contain an usher without the init.d stuff to start it at hendrik> boot and keep it up. Yup, that works. Cheers, Richard -- Richard Levitte [email protected] http://richard.levitte.org/ "Life is a tremendous celebration - and I'm invited!" -- from a friend's blog, translated from Swedish