rubygem-piston 1.4.0 devel =2

Utility to manage local copies of Subversion repositories
Maintained by: tdb@FreeBSD.org
Port Added: 31 Mar 2009 11:57:21
Also Listed In: rubygems
License: not specified in port

---

---

Piston is a utility that eases vendor branch management. This is
similar to svn:externals, except you have a local copy of the files,
which you can modify at will. As long as the changes are mergeable,
you should have no problems.

Piston has a similar purpose than svnmerge.py which you can find in
the contrib/client-side folder of the main Subversion. The main
difference is that Piston is designed to work with remote
repositories.

WWW: http://francois.github.com/piston

CVSWeb : Sources : Main Web Site : Distfiles Availability : PortsMon

---

NOTE: FreshPorts displays only required dependencies information. Optional dependencies are not covered.
Required To Build: devel/ruby-gems, lang/ruby18
Required To Run: devel/ruby-gems, lang/ruby18, lang/ruby18
There are no ports dependent upon this port

---

To install the port: cd /usr/ports/devel/rubygem-piston/ && make install clean
To add the package: pkg_add -r rubygem-piston

---

Configuration Options

     No options to configure

---

Master Sites:

http://production.s3.rubygems.org/gems/

http://production.cf.rubygems.org/gems/

ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/rubygem/

- Removing remaining MD5 from rubygem- ports

- Mass fixup of WWW: lines pkg-descr based on rubygems.org Homepage meta info

Prompted by:    distilator
With Hat:       ruby@
Sponsored by:   RideCharge Inc. / TaxiMagic

- Mass conversion of RF -> RG for MASTER_SITE for rubygem- ports
  [RG aka rubygems.org]

PR:             ports/147005
Submitted by:   pgollucci (myself)
Approved by:    portmgr (pav)
With Hat:       ruby@

- Add Piston:

        Piston is a utility that eases vendor branch management. This is
        similar to svn:externals, except you have a local copy of the files,
        which you can modify at will. As long as the changes are mergeable,
        you should have no problems.

        Piston has a similar purpose than svnmerge.py which you can find in
        the contrib/client-side folder of the main Subversion. The main
        difference is that Piston is designed to work with remote
        repositories.

        WWW: http://piston.rubyforge.org/

12 vulnerabilities affecting 17 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities