
Why oh why do we need yet another depository program? I can handle svn. I can even handle cmake, though it is a pain. But why not make the nightly update of Inkscape 48 available as a plain old tar ball?
The leaders of this project need to understand that users like me use a lot of open source software, Open COBOL, Tiny COBOL, Gimp, Scribus, Gvim, Mozilla in all its variants, Tcl/Tk and so on. Most of these projects stick to the familiar ./configure, make, make install sequence. Scribus just to be difficult insists on the cmake route, and I have finally puzzled that out. I can handle svn (replacement for cvs) with a little help. But what is Bazaar (perhaps bizarre would be a better name) and who else uses it?
I guess I will wait for the official release of Ink 48. (Grumble)

John,
Bzr is actually pretty simple to use, if you're just updating your source tree to compile. Look at
http://wiki.inkscape.org/wiki/index.php/Working_with_Bazaar
under "Using a centralized (SVN-like) workflow" to see how easy it is (pretty much what you're used to with svn).
JF
John Culleton wrote:
Why oh why do we need yet another depository program? I can handle svn. I can even handle cmake, though it is a pain. But why not make the nightly update of Inkscape 48 available as a plain old tar ball?
The leaders of this project need to understand that users like me use a lot of open source software, Open COBOL, Tiny COBOL, Gimp, Scribus, Gvim, Mozilla in all its variants, Tcl/Tk and so on. Most of these projects stick to the familiar ./configure, make, make install sequence. Scribus just to be difficult insists on the cmake route, and I have finally puzzled that out. I can handle svn (replacement for cvs) with a little help. But what is Bazaar (perhaps bizarre would be a better name) and who else uses it?
I guess I will wait for the official release of Ink 48. (Grumble)

On Tue, 6 Apr 2010 12:00:37 -0400 John Culleton <john@...1668...> wrote:
Why oh why do we need yet another depository program? I can handle svn. I can even handle cmake, though it is a pain. But why not make the nightly update of Inkscape 48 available as a plain old tar ball?
bzr makes life easier for developers relative to svn, but I agree a nightly .zip of a package is nice for people who are not developers, or at least not developers in this context, but who know enough to get things compiled.
I have some not very smart but works ok bash/python scripts for maintaining a small set of nightly snapshots from a bzr repo. They make this page: http://www.greygreen.org/leo/ and use a bzr shared repo so the server isn't pulling the full repo every night, just the changes.
I don't think I have the bandwidth for an inkscape snapshot, but if anyone wants the scripts they're welcome. Or perhaps it's sufficient to use the bzr export command, if anyone has a server, that is.
Cheers -Terry
participants (3)
-
John Culleton
-
Joshua Facemyer
-
Terry Brown