Home / Browse / Panorama Tools / Mail / Archive

Panorama Tools

Email Archive: panotools-devel (read-only)

[PanoTools-devel] subversion migration

From: dmg <dmgerman@uv...> - 2006-06-30 09:07

Hi everybody,

I have migrated the CVS repository to subversion (using cvs2svn).

In order to check the new module you will need to do the following:

svn co https://svn.sourceforge.net/svnroot/panotools/trunk/libpano libpano

I suggest you all try retrieving a working copy of the repository. 

The CVS repository is still active, by the way, so it will be a good
idea to stop any work on it until we settle on the new environment.

Bruno or Jim, would you mind giving me write access to the SVN
repository? I can read it, but I can't write to it. 




--
daniel



--
Daniel M. German                  "The energy of the world is constant.
   Rudolf Clausius ->              Its entropy tends to a maximum."
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .

Thread View

Thread	Author	Date
[PanoTools-devel] subversion migration	dmg <dmgerman@uv...>

Re: [PanoTools-devel] subversion migration

From: Bruno Postle <bruno@po...> - 2006-06-30 09:21

On Fri 30-Jun-2006 at 02:07 -0700, dmg wrote:
>
> Bruno or Jim, would you mind giving me write access to the SVN
> repository? I can read it, but I can't write to it. 

Ok, everyone who previously had CVS access now has SVN access.

Note that we might restrict this access in future if somebody takes 
on a role as 'commit manager'.

Also if anyone thinks they should be a 'project admin', then we can 
extend this (currently Jim and myself have project admin access).

-- 
Bruno

Re: [PanoTools-devel] subversion migration

From: Daniel M. German <dmgerman@uv...> - 2006-06-30 14:35

Bruno> On Fri 30-Jun-2006 at 02:07 -0700, dmg wrote:
 >> 
 >> Bruno or Jim, would you mind giving me write access to the SVN
 >> repository? I can read it, but I can't write to it. 

 Bruno> Ok, everyone who previously had CVS access now has SVN access.

Thanks Bruno,

I was about to create a branch for libpano12, but I am not sure where
to branch.  I suggested branching before we introduced cropped
tiffs. What do other people think? Use svn log. You will immediately
see the advantages of svn. Under svn it is very easy to branch at any
given revision number.

By the way, the new layout of the repository is appended at the end.

* The tags directory contains the versions of the tools as they were
 released. 

* The branches contain the few branches some people have created

* The main development area is trunk. To retrieve only libpano you
  have to:

svn co https://svn.sourceforge.net/svnroot/panotools/trunk/libpano libpano

If you want to see the entire repository do:

svn co https://svn.sourceforge.net/svnroot/panotools <directory>

|-- branches
[..]
|-- tags
[..]
`-- trunk
    |-- CVSROOT
    |-- Panotools-Script
    |   |-- bin
    |   |-- lib
    |   |   `-- Panotools
    |   |       `-- Script
    |   |           `-- Line
    |   `-- t
    |       `-- data
    |           `-- cemetery
    |-- clens
    |   |-- data
    |   |-- doc
    |   |   `-- developer
    |   |       `-- html
    |   |-- include
    |   |-- m4
    |   `-- src
    |-- gimp-plugin
    |-- gimp-plugin-ng
    |   |-- help
    |   |   |-- images
    |   |   |-- stylesheets
    |   |   `-- xml
    |   |-- po
    |   `-- src
    |-- libpano
    |   |-- build
    |   |   `-- win32
    |   |-- doc
    |   |-- m4
    |   |-- tests
    |   |   `-- simpleStitch
    |   |       `-- reference
    |   `-- tools
    `-- ptfilter
        |-- PTAdjust
        |-- PTCorrect
        |-- PTPerspect
        `-- PTRemap

--
Daniel M. German
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .

Re: [PanoTools-devel] subversion migration

From: Bruno Postle <bruno@po...> - 2006-06-30 14:40

Daniel M. German wrote:
> 
> I was about to create a branch for libpano12, but I am not sure where
> to branch.  I suggested branching before we introduced cropped
> tiffs. What do other people think?

Since there is not going to be a maintained PTmender that works with 
the PTStitcher-compatible pano12.dll, the cropped TIFF stuff doesn't 
really matter.

If somebody wants to use cropped TIFF, then they will be using the 
new library from the trunk.

So the branch can start at the point before binary-incompatability 
happened.

-- 
Bruno

Re: [PanoTools-devel] subversion migration

From: Daniel M. German <dmgerman@uv...> - 2006-06-30 14:57

Bruno> Daniel M. German wrote:
 >> 
 >> I was about to create a branch for libpano12, but I am not sure where
 >> to branch.  I suggested branching before we introduced cropped
 >> tiffs. What do other people think?

 Bruno> Since there is not going to be a maintained PTmender that works with 
 Bruno> the PTStitcher-compatible pano12.dll, the cropped TIFF stuff doesn't 
 Bruno> really matter.

 Bruno> If somebody wants to use cropped TIFF, then they will be using the 
 Bruno> new library from the trunk.

 Bruno> So the branch can start at the point before binary-incompatability 
 Bruno> happened.

Ok, I have branched the entire repository at the following revision:

----------------------------------------------------------------------
r516 | brunopostle | 2006-06-14 13:17:44 -0700 (Wed, 14 Jun 2006) | 2 lines

Put tests in tarball, but only run them with 'make check'.
----------------------------------------------------------------------

I have called the branch pano12 but the name can be changed if we
decide for a better name (renaming is easy in svn). I have branched
all the modules in panotools:

----------------------------------------------------------------------
drwxrwxr-x 8 dmg dmg 4.0K Jun 30 07:49 clens/
drwxrwxr-x 3 dmg dmg 4.0K Jun 30 07:49 CVSROOT/
drwxrwxr-x 3 dmg dmg 4.0K Jun 30 07:50 gimp-plugin/
drwxrwxr-x 6 dmg dmg 4.0K Jun 30 07:50 gimp-plugin-ng/
drwxrwxr-x 8 dmg dmg 4.0K Jun 30 07:50 libpano/
drwxrwxr-x 6 dmg dmg 4.0K Jun 30 07:49 Panotools-Script/
drwxrwxr-x 7 dmg dmg 4.0K Jun 30 07:50 ptfilter/
----------------------------------------------------------------------

Perhaps we might want to delete some (like CVSROOT) or all except
libpano. I guess at this point it does not harm to keep them all.

the command to retrieve the branch is:

svn co https://svn.sourceforge.net/svnroot/panotools/branches/pano12 pano12

I'll start backing up the new repository tonight (I have been backing
up the CVS one). 

Bruno, is there a way to "close" write access to the CVS repository? 

--
daniel

--
Daniel M. German                  "I see no good reason why the
                                   views given in this volume
                                   should shock the religious
   Charles Darwin ->               feelings of anyone."
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .

Re: [PanoTools-devel] subversion migration

From: Bruno Postle <bruno@po...> - 2006-06-30 15:54

On Fri 30-Jun-2006 at 07:56 -0700, Daniel M. German wrote:
>
> I have branched all the modules in panotools:
>
> drwxrwxr-x 8 dmg dmg 4.0K Jun 30 07:49 clens/
> drwxrwxr-x 3 dmg dmg 4.0K Jun 30 07:49 CVSROOT/
> drwxrwxr-x 3 dmg dmg 4.0K Jun 30 07:50 gimp-plugin/
> drwxrwxr-x 6 dmg dmg 4.0K Jun 30 07:50 gimp-plugin-ng/
> drwxrwxr-x 8 dmg dmg 4.0K Jun 30 07:50 libpano/
> drwxrwxr-x 6 dmg dmg 4.0K Jun 30 07:49 Panotools-Script/
> drwxrwxr-x 7 dmg dmg 4.0K Jun 30 07:50 ptfilter/

> Perhaps we might want to delete some (like CVSROOT) or all except
> libpano. I guess at this point it does not harm to keep them all.

There is no need to branch for any except libpano.  Also do we want 
to move all the 'panotools' projects to subversion?  or just libpano?

Does anyone need help with this switch from CVS to subversion?  I 
guess it might be confusing if you are not familiar with all this 
stuff.

> Bruno, is there a way to "close" write access to the CVS repository? 

Yes, each developer can have their CVS access withrawn, so we can do 
this if we are moving everything to subversion permanently.

-- 
Bruno

Re: [PanoTools-devel] subversion migration

From: Jim Watters <jwatters@ph...> - 2006-06-30 16:51

On Fri, June 30, 2006 11:54 am, Bruno Postle said:
>> I have branched all the modules in panotools:
>>
>> drwxrwxr-x 8 dmg dmg 4.0K Jun 30 07:49 clens/
>> drwxrwxr-x 3 dmg dmg 4.0K Jun 30 07:49 CVSROOT/
>> drwxrwxr-x 3 dmg dmg 4.0K Jun 30 07:50 gimp-plugin/
>> drwxrwxr-x 6 dmg dmg 4.0K Jun 30 07:50 gimp-plugin-ng/
>> drwxrwxr-x 8 dmg dmg 4.0K Jun 30 07:50 libpano/
>> drwxrwxr-x 6 dmg dmg 4.0K Jun 30 07:49 Panotools-Script/
>> drwxrwxr-x 7 dmg dmg 4.0K Jun 30 07:50 ptfilter/
>
>> Perhaps we might want to delete some (like CVSROOT) or all except
>> libpano. I guess at this point it does not harm to keep them all.
My old attempt at making PTStitcher should be removed.  Daniel's PTMender is the way of
the future.

I would like to put the various tools into seperate folders.

> There is no need to branch for any except libpano.  Also do we want
> to move all the 'panotools' projects to subversion?  or just libpano?

The change in the structure will likely effect clens, plugin, and ptfilter.  I think we
need to keep everything branched.  Not looking at the code to be sure.


> Does anyone need help with this switch from CVS to subversion?  I
> guess it might be confusing if you are not familiar with all this
> stuff.

I think the hardest part of setting my computer back up with a development enviroment
was getting the CVS working correctly.  I use subversion a little bit at work already so
I hope this wont be an issue for me.

>> Bruno, is there a way to "close" write access to the CVS repository?
>
> Yes, each developer can have their CVS access withrawn, so we can do
> this if we are moving everything to subversion permanently.

I think everything has been moved.


-- 
Jim Watters

Yahoo ID: j1vvy ymsgr:sendIM?j1vvy
jwatters @ photocreations . ca
http://photocreations.ca