Jppy: jpilot_src/CVS

[Nicholas Piper]

martin,

On Tue, 06 Mar 2007, martin f krafft wrote:

> The SVN source for jppy includes a CVS checkout in jpilot_src, and
> the entire CVS directory is checked into SVN itself. This seems
> awful, but there is probably a good reason for it as I assume the
> source is needed to build the plugins. I wonder though whether there
> wouldn't be a more SVN-friendly way to handle the situation... the
> best would obviously be to make the J-Pilot dudes produce jpilot-dev
> but that's a long-term and possibly too ideological goal. So
> instead, wouldn't it be possible to just check in and sync from the
> tarballs?

I've considered a few times making more of jpilot into a shared
library, then asking Judd to take that patch. I've not done it yet
though.

(The source isn't needed to build jpilot _plugins_, it's more needed
for the python shared library. That needs to use core jpilot code, so
it actually does include that code.)

Including the CVS details in SVN doesn't seem too bad to me. I can
then easily 'cvs update', as well as make patches if required.

Having a tarball binary in svn seems worse, I strongly don't like
binary files in version control systems.

If jpilot's development used svn, then I'd probably use svn:externals
which pointed at one of their tags.

 Nick

-- 
Nick Piper, Developer, LogicaCMG           http://www.nickpiper.co.uk/
GPG Encrypted mail welcome!                             1024D/3ED8B27F
Choose life. Be Vegan :-) Please reduce needless cruelty & suffering !