CVS log for pkgsrc/devel/ruby-path/Attic/PLIST
Up to [cvs.NetBSD.org] / pkgsrc / devel / ruby-path
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
Revision 1.2
Mon Nov 4 04:23:06 2019 UTC (7 years ago) by taca
Branches: MAIN
CVS tags: HEAD
FILE REMOVED
Changes since revision 1.1: +1 -1
lines
devel/ruby-path: remove package
Remove ruby-path package.
Initially, it was added for some other ruby packge depdendency but now no
package depends on it. And this package is not maintained and no new
rubygems.
Revision 1.1: download - view: text, markup, annotated - select for diffs
Mon Feb 11 08:51:00 2013 UTC (13 years, 9 months ago) by taca
Branches: MAIN
CVS tags: pkgsrc-2019Q3-base,
pkgsrc-2019Q3,
pkgsrc-2019Q2-base,
pkgsrc-2019Q2,
pkgsrc-2019Q1-base,
pkgsrc-2019Q1,
pkgsrc-2018Q4-base,
pkgsrc-2018Q4,
pkgsrc-2018Q3-base,
pkgsrc-2018Q3,
pkgsrc-2018Q2-base,
pkgsrc-2018Q2,
pkgsrc-2018Q1-base,
pkgsrc-2018Q1,
pkgsrc-2017Q4-base,
pkgsrc-2017Q4,
pkgsrc-2017Q3-base,
pkgsrc-2017Q3,
pkgsrc-2017Q2-base,
pkgsrc-2017Q2,
pkgsrc-2017Q1-base,
pkgsrc-2017Q1,
pkgsrc-2016Q4-base,
pkgsrc-2016Q4,
pkgsrc-2016Q3-base,
pkgsrc-2016Q3,
pkgsrc-2016Q2-base,
pkgsrc-2016Q2,
pkgsrc-2016Q1-base,
pkgsrc-2016Q1,
pkgsrc-2015Q4-base,
pkgsrc-2015Q4,
pkgsrc-2015Q3-base,
pkgsrc-2015Q3,
pkgsrc-2015Q2-base,
pkgsrc-2015Q2,
pkgsrc-2015Q1-base,
pkgsrc-2015Q1,
pkgsrc-2014Q4-base,
pkgsrc-2014Q4,
pkgsrc-2014Q3-base,
pkgsrc-2014Q3,
pkgsrc-2014Q2-base,
pkgsrc-2014Q2,
pkgsrc-2014Q1-base,
pkgsrc-2014Q1,
pkgsrc-2013Q4-base,
pkgsrc-2013Q4,
pkgsrc-2013Q3-base,
pkgsrc-2013Q3,
pkgsrc-2013Q2-base,
pkgsrc-2013Q2,
pkgsrc-2013Q1-base,
pkgsrc-2013Q1
Add ruby-path package version 1.3.1.
Path - a Path manipulation library
Path is a library to manage paths. It is similar to Pathname, but has some
extra goodness. The method names are intended to be short and explicit, and
avoid too much duplication like having 'name' or 'path' in the method name.
I believe the object-oriented approach to manipulate paths is very elegant and
useful. Paths are naturally the subject of their methods and even if they are
simple Strings behind, they carry way much more information and deserve a
first-class status.
Also, using a path library like this avoid to remember in which class the
functionality is implemented, everything is in one place (if not, please open
an issue!).
CVSweb <webmaster@jp.NetBSD.org>