Pidgin

On Mon, 2006-10-23 at 13:52 -0700, Sean Egan wrote:
> This is just a reminder that aynone checking in a change to SF svn
> should also be checking that same change into pidgin.im.

What's the URL for SVN on pidgin.im?

Are all the developers on this list, or are Mark H., Bartosz, and Thomas
in the dark on this?

Why is this necessary anyway? Has anything new been committed to the
pidgin.im SVN repository? Couldn't we just wait until it's time to go
live with it and: 1) dump the repository from SF, 2) load it on
pidgin.im, and 3) do the Gaim -> Pidgin rename?

Richard

On 10/23/06, Richard Laager <rlaager@...> wrote:
> Are all the developers on this list, or are Mark H., Bartosz, and Thomas
> in the dark on this?

They are in the dark. I'll bring them in.

> Why is this necessary anyway? Has anything new been committed to the
> pidgin.im SVN repository?

Yes. A bunch of rename changes and all the icon changes. It's very
incomplete right now.

> Couldn't we just wait until it's time to go
> live with it and: 1) dump the repository from SF, 2) load it on
> pidgin.im, and 3) do the Gaim -> Pidgin rename?

Because I want the renaming/icon changes to be in svn so that other
people can use and hack on it. Step 3 is more complicated than you're
letting on to.

-s.

On 10/23/06, Sean Egan <seanegan@...> wrote:
> This is just a reminder that aynone checking in a change to SF svn
> should also be checking that same change into pidgin.im.
>
> Penguin poitns to whoever writes a script to do it automatically.

There is a utility that we can use to make this easy:
http://svn.collab.net/repos/svn/trunk/contrib/client-side/svn-push/svn-push.c

I don't have an etch box to compile it on and I didn't want to install
all the necessary dev packages on pidgin.im if there was somewhere
else that this could be compiled.  Does someone have an etch box that
they can use to build this for us?

-D

On Mon, 2006-10-23 at 14:28 -0700, Sean Egan wrote:
> Because I want the renaming/icon changes to be in svn so that other
> people can use and hack on it. Step 3 is more complicated than you're
> letting on to.

Fair enough.

It looks like the "branch" happened at 17548. Is there some intelligent
way to pull in 17549-HEAD from Gaim SVN to Pidgin SVN? Alternatively, do
we want to apply one bit changeset, or apply them individually?

/me wishes we were already using a distributed VCS, where this would be
easy.

Richard

Richard Laager spake unto us the following wisdom:
> /me wishes we were already using a distributed VCS, where this would be
> easy.

Incidentally, I've been tailor'ing over to monotone for some time
now.[1]  We could always switch SCMs in the process...  ;-)

Ethan

[1] Excepting state before the revisions across which svn cannot even
    update for itself ... which is a lot.  Subversion has pretty much
    hosed our ability to ever losslessly switch to another VCS.

--=20
The laws that forbid the carrying of arms are laws [that have no remedy
for evils].  They disarm only those who are neither inclined nor
determined to commit crimes.
		-- Cesare Beccaria, "On Crimes and Punishments", 1764

On Mon, 2006-10-23 at 18:53 -0400, Ethan Blanton wrote:
> Richard Laager spake unto us the following wisdom:
> > /me wishes we were already using a distributed VCS, where this would be
> > easy.
>=20
> Incidentally, I've been tailor'ing over to monotone for some time
> now.[1]  We could always switch SCMs in the process...  ;-)

I think now would be a good time to give Monotone a try. Ethan suggested
using tailor to copy the trunk to SVN, so that "casual developers"/"itch
scratchers"/whatever-you-want-to-call-them don't have to checkout the
entire revision history. That sounds reasonable to me.

=46rom my talk with a couple Monotone developers, I became pretty excited
about Monotone with respect to the potential for workflow enhancements
in the future. Also from what I gather, Subversion is aiming to be just
CVS++. While that's enough in a lot of scenarios, I think we could gain
something from a distributed VCS.

Richard