| Port details |
- rubygem-piston Utility to manage local copies of Subversion repositories
- 1.4.0 devel
 =1      1.4.0Version of this port present on the latest quarterly branch.  DEPRECATED: No longer maintained upstream
 This port expired on: 2018-02-08
- Maintainer: tdb@FreeBSD.org
- Port Added: 2009-03-31 11:57:21
- Last Update: 2018-02-10 22:03:15
- SVN Revision: 461438
- People watching this port, also watch:: sysinfo, rtty, tmpreaper, svk
- Also Listed In: rubygems
- License: not specified in port
- WWW:
- http://francois.github.com/piston
- Description:
- 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
 cgit ¦ GitHub ¦ GitHub ¦ GitLab ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - Dependency lines:
-
- rubygem-piston>0:devel/rubygem-piston
- No installation instructions:
- This port has been deleted.
- PKGNAME: rubygem-piston
- Flavors: there is no flavor information for this port.
- distinfo:
- SHA256 (rubygem/piston-1.4.0.gem) = 7d86d9e68dac5065cfb9160e24f073935dc85261a08f300e34e62b918537e230
SIZE (rubygem/piston-1.4.0.gem) = 16896
No package information for this port in our database- Sometimes this happens. Not all ports have packages.
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- ruby24 : lang/ruby24
- gem24 : devel/ruby-gems
- Runtime dependencies:
-
- ruby24 : lang/ruby24
- gem24 : devel/ruby-gems
- Patch dependencies:
-
- ruby24 : lang/ruby24
- gem24 : devel/ruby-gems
-
- There are no ports dependent upon this port
Configuration Options:- No options to configure
- Options name:
- N/A
- USES:
- gem
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
1.4.0
10 Feb 2018 22:03:15
   |
rene |
Remove expired ports:
2018-01-01 devel/p5-Parse-Pidl: yes
2018-02-08 devel/rubygem-piston: No longer maintained upstream
2017-04-05 databases/postgresql92-server: PostgreSQL 9.2 support has reached
End-of-line. Please upgrade to a later version. |
1.4.0
08 Jan 2018 16:11:34
|
swills |
devel/rubygem-piston: Mark deprecated and set expiration
Approved by: tdb (private email) |
1.4.0
27 Apr 2016 21:57:32
|
swills |
Convert USES=gem:autoplist to USES=gem since autoplist is default |
1.4.0
27 Apr 2016 16:36:42
|
swills |
create USES=gem and update rubygem- ports to use it
Note that for now ports still have to have USE_RUBY=yes to use USES=gem
PR: 209041
Differential Revision: https://reviews.freebsd.org/D6070 |
1.4.0
02 Jul 2015 16:01:08
|
pgollucci |
Set NO_ARCH for remaining rubygem-* ports with no arch dependent files
Obtained from: DEVELOPER_MODE
With Hat: ruby@
Sponsored by: RideCharge Inc / Curb |
1.4.0
24 Jan 2014 14:47:11
|
miwi |
- Stage safe |
1.4.0
20 Sep 2013 17:17:45
|
bapt |
Add NO_STAGE all over the place in preparation for the staging support (cat:
devel part 4) |
1.4.0
23 Jun 2011 18:03:54
|
pgollucci |
- Removing remaining MD5 from rubygem- ports |
1.4.0
20 Oct 2010 01:35:47
|
pgollucci |
- 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 |
1.4.0
26 May 2010 19:51:35
|
pgollucci |
- 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@ |
1.4.0
31 Mar 2009 11:56:52
|
tdb |
- 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/ |
As an Amazon Associate I earn from qualifying purchases.