Subversion migration

17 years ago by Ilia Cheishvili — view source — reply

unread

As far as I know, it's still underway. Andi explained at ZendCon this year
how it will take a few more months--he made it clear that PHP has a very
rich development history that no one wants to lose. I, for one, am looking
forward to when the migration is finally complete, as I am so much more used
to Subversion than CVS :)

Ilia

On Mon, Sep 22, 2008 at 10:13 PM, Andrei Zmievski andrei@gravitonic.comwrote:

Whatever happened to the Subversion migration effort?

-Andrei

17 years ago by David Soria Parra — view source — reply

unread

Andrei Zmievski wrote:

Whatever happened to the Subversion migration effort?

-Andrei

As far as I know the actual conversion is done, but a lot of the
CVSROOT/ scripts are not yet rewritten to fit the subversion hook
system. Also Marcus proposed and I guess it was somehow accepted, that
the new scripts are done in Python and not in Perl.

               David

17 years ago by Antony Dovgal — view source — reply

unread

As far as I know the actual conversion is done, but a lot of the
CVSROOT/ scripts are not yet rewritten to fit the subversion hook
system. Also Marcus proposed and I guess it was somehow accepted, that
the new scripts are done in Python and not in Perl.

I've heard of a language once, they say it's quite easy to learn, it has a
comprehensive documentation and large userbase.. It's called PPH or something.
Maybe we should use it instead of Python?

Seriously, I thought we've had enough problems with viewvc.cgi,
why not use something that's easier to tweak & maintain (for us)?

--
Wbr,
Antony Dovgal

17 years ago by Alexey Zakhlestin — view source — reply

unread

As far as I know the actual conversion is done, but a lot of the
CVSROOT/ scripts are not yet rewritten to fit the subversion hook
system. Also Marcus proposed and I guess it was somehow accepted, that
the new scripts are done in Python and not in Perl.

I've heard of a language once, they say it's quite easy to learn, it has a
comprehensive documentation and large userbase.. It's called PPH or something.
Maybe we should use it instead of Python?

Seriously, I thought we've had enough problems with viewvc.cgi,
why not use something that's easier to tweak & maintain (for us)?

+1
we can use http://pecl.php.net/package/svn for this. It is marked as
beta, but in my experience it is very solid.

--
Alexey Zakhlestin
http://blog.milkfarmsoft.com/

17 years ago by zoe.slattery@googlemail.com — view source — reply

unread

David Soria Parra wrote:

As far as I know the actual conversion is done, but a lot of the
CVSROOT/ scripts are not yet rewritten to fit the subversion hook
system. Also Marcus proposed and I guess it was somehow accepted, that
the new scripts are done in Python and not in Perl.

Is there a list of what needs to be written? I have some spare time and
could help, although I confess I'd prefer to write in PHP.

Zoe

17 years ago by Lukas Kahwe Smith — view source — reply

unread

David Soria Parra wrote:

As far as I know the actual conversion is done, but a lot of the
CVSROOT/ scripts are not yet rewritten to fit the subversion hook
system. Also Marcus proposed and I guess it was somehow accepted,
that the new scripts are done in Python and not in Perl.

Is there a list of what needs to be written? I have some spare time
and could help, although I confess I'd prefer to write in PHP.

i would agree that PHP should be the preferred language unless we
could spare a lot of work with using something existing and adapting
it .. but even then the goal should be to eat as much of our own
dogfood for this .. seems like there is nothing that would be so heavy
(or long running) to make PHP totally unfit for this.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org

17 years ago by Maciek Sokolewicz — view source — reply

unread

Lukas Kahwe Smith wrote:

David Soria Parra wrote:

As far as I know the actual conversion is done, but a lot of the
CVSROOT/ scripts are not yet rewritten to fit the subversion hook
system. Also Marcus proposed and I guess it was somehow accepted,
that the new scripts are done in Python and not in Perl.

Is there a list of what needs to be written? I have some spare time
and could help, although I confess I'd prefer to write in PHP.

i would agree that PHP should be the preferred language unless we could
spare a lot of work with using something existing and adapting it .. but
even then the goal should be to eat as much of our own dogfood for this
.. seems like there is nothing that would be so heavy (or long running)
to make PHP totally unfit for this.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org

There has been a (short) discussion about this on the svn-migration
mailinglist (cc'd) which resulted in the recommendation of writing it
either in Python (because subversion uses that natively) or PHP (since
we don't like the whole perl clog that's in there right now).

The migration process seems to have ground to a standstill lately
(judging by the amount of posts to that list in the last month (last one
being at the start of september)), but all help is appreciated. Please
join that mailinglist so we can all work together and not be forced to
re-post every idea and option twice (internals and svn-migration) just
because people don't read the list.

Tul

17 years ago by Antony Dovgal — view source — reply

unread

There has been a (short) discussion about this on the svn-migration
mailinglist (cc'd) which resulted in the recommendation of writing it
either in Python (because subversion uses that natively)

What exactly do you mean by that?

Does Subversion have any scripts we need already implemented in Python?
If not, I don't see why should we even care what Subversion uses.

We have our own needs and I see nothing wrong in using PHP for
sending commit logs to the list, doing authorization and updating
the changelog, do you?

--
Wbr,
Antony Dovgal

17 years ago by Maciek Sokolewicz — view source — reply

unread

Antony Dovgal wrote:

There has been a (short) discussion about this on the svn-migration
mailinglist (cc'd) which resulted in the recommendation of writing it
either in Python (because subversion uses that natively)

What exactly do you mean by that?

Does Subversion have any scripts we need already implemented in Python?
If not, I don't see why should we even care what Subversion uses.

We have our own needs and I see nothing wrong in using PHP for
sending commit logs to the list, doing authorization and updating
the changelog, do you?

By that I meant that several scripts which come with subversion are
written in Python. They're pretty easy to replace with PHP scripts
though if we do decide to use eg. the pecl svn extension. We would need
to modify them extensively anyway if we were to use a system analogous
to the one in use in CVS now (avail system comes to mind), so rewriting
them in PHP would probably take the same amount of time/effort. I
personally wouldn't mind using PHP at all (would even prefer it as I
wrote in my original mail to svn-migration).

17 years ago by David Coallier — view source — reply

unread

By that I meant that several scripts which come with subversion are written
in Python. They're pretty easy to replace with PHP scripts though if we do
decide to use eg. the pecl svn extension. We would need to modify them
extensively anyway if we were to use a system analogous to the one in use in
CVS now (avail system comes to mind), so rewriting them in PHP would
probably take the same amount of time/effort. I personally wouldn't mind
using PHP at all (would even prefer it as I wrote in my original mail to
svn-migration).

Could we please move this discussion to the svn.migration list please?

Thanks,

--
Slan,
David