Re: [Monotone-devel] monotone-usher or usher-server and usher

2011-12-27 Thread Richard Levitte
In message jdbb5r$ejl$2...@dough.gmane.org on Tue, 27 Dec 2011 02:39:56 + 
(UTC), Hendrik Boom hend...@topoi.pooq.com said:

hendrik On Tue, 27 Dec 2011 01:26:42 +, Hendrik Boom wrote:
hendrik 
hendrik  On Tue, 20 Dec 2011 10:21:19 +0100, Richard Levitte wrote:
hendrik  
hendrik  In message 87r500w9om@ludovic-brenta.org on Mon, 19 Dec 2011
hendrik  22:09:13 +0100, Ludovic Brenta ludo...@ludovic-brenta.org 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
hendrikorg.debian.usher
hendrikorg.debian.experimental

Correction: org.debian.usher.experimental

hendrik  and
hendriknet.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 rich...@levitte.org
http://richard.levitte.org/

Life is a tremendous celebration - and I'm invited!
-- from a friend's blog, translated from Swedish

___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel


Re: [Monotone-devel] monotone-usher or usher-server and usher

2011-12-27 Thread Hendrik Boom
On Tue, 27 Dec 2011 11:40:16 +0100, Richard Levitte wrote:

 
 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)

So this means I make nested checkouts, without using merge-into-dir
which was supposed to replace nested checkouts.

Is there any documentation on how nested workspaces are supposed to work?

Are these projects sufficiently disjoint that I should keep them in 
separate databases following the each-project-has-its-own-database 
best-practice? Might it make netsync awkward if I don't keep them
separate? Does the local database keep track of which other database 
separate for each branch, or is it just one for all?

-- hendrik


___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel