Update of /cvsroot/fink/dists/10.7/stable/main/finkinfo/libs/pythonmods
In directory vz-cvs-3.sog:/tmp/cvs-serv28187

Added Files:
        cvs2svn-py.info 
Log Message:
Move to 10.7.


--- NEW FILE: cvs2svn-py.info ---
Info2: <<
Package: cvs2svn-py%type_pkg[python]
Version: 2.3.99.5319
Revision: 1
#Fink's python25 doesn't build module mmap so we require 26 or later.
Type: python (2.6 2.7)
Description: CVS to SVN/git/bzr/hg repository converter
License: BSD
Maintainer: Daniel Johnson <[email protected]>

# Dependencies:
BuildDepends: fink (>= 0.24.12)
Depends: svn (>= 1.6.9-1), python%type_pkg[python]
Recommends: git, bzr-py%type_pkg[python], mercurial-py%type_pkg[python]
Conflicts: %{Ni}23-bin, %{Ni}24-bin, %{Ni}25-bin 
Replaces: %{Ni}23-bin, %{Ni}24-bin, %{Ni}25-bin

# Unpack Phase:
#Source: http://cvs2svn.tigris.org/files/documents/1462/46528/cvs2svn-%v.tar.gz
Source: http://homepage.mac.com/danielj7/cvs2svn-%v.tar.bz2
Source-MD5: 6f7325c7a289703aaa739c9f09b3ecdc
SourceDirectory: cvs2svn

# Compile Phase:
CompileScript: <<
 python%type_raw[python] setup.py build
<<

InfoTest: <<
 TestScript: make check PYTHON=%p/bin/python%type_raw[python] || exit 2
<<

# Install Phase:
DocFiles: BUGS CHANGES COMMITTERS COPYING HACKING README *example.options 
contrib/*
InstallScript: <<
# This needs to be run after TestScript or it gets wiped out.
 perl -pi -e 's;#!/usr/bin/env python;#!%p/bin/python%type_raw[python];' 
cvs2svn cvs2git cvs2bzr
 make man PYTHON=%p/bin/python%type_raw[python]

 make install DESTDIR=%d PYTHON=%p/bin/python%type_raw[python]
 mv %i/bin/cvs2svn %i/bin/cvs2svn-py%type_pkg[python]
 mv %i/bin/cvs2git %i/bin/cvs2git-py%type_pkg[python]
 mv %i/bin/cvs2bzr %i/bin/cvs2bzr-py%type_pkg[python]

 # Install verify-cvs2svn
 perl -pi -e 's;#!/usr/bin/env python;#!%p/bin/python%type_raw[python];' 
contrib/verify-cvs2svn.py
 /usr/bin/install -m 755 contrib/verify-cvs2svn.py 
%i/bin/verify-cvs2svn-py%type_pkg[python]
 
 ### Install docu
 /usr/bin/install -m 755 -d %i/share/doc/%n
 cp -r www %i/share/doc/%n
 chmod ugo+r %i/share/doc/%n/www
 /usr/bin/install -m 755 -d %i/share/man/man1
 /usr/bin/install -m 644 cvs2svn.1 
%i/share/man/man1/cvs2svn.1-py%type_pkg[python]
 /usr/bin/install -m 644 cvs2git.1 
%i/share/man/man1/cvs2git.1-py%type_pkg[python]
 /usr/bin/install -m 644 cvs2bzr.1 
%i/share/man/man1/cvs2bzr.1-py%type_pkg[python]

<<
PostInstScript: <<
        update-alternatives --install %p/bin/cvs2svn cvs2svn 
%p/bin/cvs2svn-py%type_pkg[python] %type_pkg[python] --slave 
%p/share/man/man1/cvs2svn.1 cvs2svn.1 
%p/share/man/man1/cvs2svn.1-py%type_pkg[python] --slave %p/bin/verify-cvs2svn 
verify-cvs2svn %p/bin/verify-cvs2svn-py%type_pkg[python]
        update-alternatives --install %p/bin/cvs2git cvs2git 
%p/bin/cvs2git-py%type_pkg[python] %type_pkg[python] --slave 
%p/share/man/man1/cvs2git.1 cvs2git.1 
%p/share/man/man1/cvs2git.1-py%type_pkg[python]
        update-alternatives --install %p/bin/cvs2bzr cvs2bzr 
%p/bin/cvs2bzr-py%type_pkg[python] %type_pkg[python] --slave 
%p/share/man/man1/cvs2bzr.1 cvs2bzr.1 
%p/share/man/man1/cvs2bzr.1-py%type_pkg[python]
<<
PreRmScript: <<
        update-alternatives --remove cvs2svn %p/bin/cvs2svn-py%type_pkg[python]
        update-alternatives --remove cvs2git %p/bin/cvs2git-py%type_pkg[python]
        update-alternatives --remove cvs2bzr %p/bin/cvs2bzr-py%type_pkg[python]
<<

# Additional Info:
DescDetail: <<
cvs2svn is a tool for migrating a CVS repository to Subversion, git,
Bazaar, or Mercurial. The main design goals are robustness and 100% data
preservation. cvs2svn can convert just about any CVS repository we've ever
seen, including gcc, Mozilla, FreeBSD, KDE, GNOME...

.. cvs2svn: http://cvs2svn.tigris.org/
.. Subversion: http://svn.tigris.org/
.. git: http://git-scm.com/
.. Bazaar: http://bazaar-vcs.org/
.. Mercurial: http://mercurial.selenic.com/

cvs2svn infers what happened in the history of your CVS repository and
replicates that history as accurately as possible in the target SCM. All
revisions, branches, tags, log messages, author names, and commit dates are
converted. cvs2svn deduces what CVS modifications were made at the same time,
and outputs these modifications grouped together as changesets in the target
SCM. cvs2svn also deals with many CVS quirks and is highly configurable.
See the comprehensive `feature list`.

.. feature list: http://cvs2svn.tigris.org/features.html
.. documentation: http://cvs2svn.tigris.org/cvs2svn.html

Please read the documentation carefully before using cvs2svn.
<<
DescUsage: <<
Type 'cvs2svn --help' or 'man cvs2svn' for help. Read the home page for more 
information - also available from 
%p/share/doc/%n/www/cvs2svn.html

To use the cvs2git and cvs2bzr tools, you need to install the
git and bzr-py%type_pkg[python] packages, respectively.

To use "cvs2hg", you need to install mercurial-py%type_pkg[python].

"cvs2hg" is shorthand for "cvs2git in the mode where it is
outputting to Mercurial instead of git".  But the program that needs
to be run is still called "cvs2git".  Run it with the --options
option, passing it this file as argument:

        cvs2git --options=%p/share/doc/%n/cvs2hg-example.options

Check your new repository carefully after conversion. Mail 
[email protected] if you encounter any problems. You can also ask
questions on IRC at irc.freenode.net, channel cvs2svn.

You may use the tool 'verify-cvs2svn' to verify your conversion. But a
WARNING: The 'verify-cvs2svn' is not yet finished. It may produce false 
warnings or ignore serious problems. Don't trust it!
<<
DescPackaging: <<
The old cvs2svn-pyXX-bin packages are re-incorporated
into the cvs2svn-pyXX packages as of 2.0.1-11.

Previously maintained by Christian Schaffner <[email protected]>

Tarball made from upstream svn revision 5319 from
http://cvs2svn.tigris.org/svn/cvs2svn/trunk
<<
Homepage: http://cvs2svn.tigris.org/cvs2svn.html

# End of Info2
<<


------------------------------------------------------------------------------
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
_______________________________________________
Fink-commits mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.cvs

Reply via email to