Compiling plugins

[Russel Winder]

I think I half asked this previously on the list but clearly I failed to
remember the content of the responses.

Some plugins are pure Python code and so having them live in
~/.bazaar/plugins presents few if any problems (Windows users please
apply the appropriate sed operation to the path :-)

Some plugins -- OK let's be open here bzr-svn -- require a compilation
stage.  This is fine if you have only one computer or you have separate
home directories for every machine you use.  Some of us however have
multiple machines of different architectures sharing a single filestore
via NFS mounting from a server.  This leads to a situation which can
only be described as "screwed".

The plugins have to be installed in ~/.bazaar/plugins and there is no
naming strategy to deal with platform specific variants.  What I need is
to have a single svn plugin directory -- so I only have to pull from
Jelmer's branch on one machine and then to be able to compile for
Ubuntu, Solaris and Mac OS X in the same source tree.

I have mentioned this to Jelmer and he cannot think of a solution to
this and suggested I hassle members of the list with problem :-)
 
Thanks.

-- 
Russel.
====================================================
Dr Russel Winder                 Partner

Concertant LLP                   t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road,              f: +44 8700 516 084
London SW11 1EN, UK.             m: +44 7770 465 077
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20080821/0920289f/attachment.pgp