Changes between Version 2 and Version 3 of RubyGems

Timestamp:

01/04/08 17:56:51 (5 years ago)

Author:

duncan

Comment:

finish sentance about traditional package managers

RubyGems

@@ -13 +13 @@
 
 
-Unlike Cabal packages, Gems require a certain directory layout. Cabal packages mostly follow the autoconf style, allowing different kinds of files to be put in various places, with one set of defaults for Unix (again like the autoconf defaults) and another set of defaults for Windows. Apparently the
+Unlike Cabal packages, Gems require a certain directory layout. Cabal packages mostly follow the autoconf style, allowing different kinds of files to be put in various places, with one set of defaults for Unix (again like the autoconf defaults) and another set of defaults for Windows. [http://rubygems.org/read/chapter/14#page62 Apparently] this makes gems hard to package in traditional package managers.
 
 == Website ==
@@ -29 +29 @@
 == `gem` command ==
 
-This is rather similar to [CabalInstall `cabal-install`]. It is a command line tool to manage the installation of gems.
+This is rather similar to [CabalInstall cabal-install]. It is a command line tool to manage the installation of gems.
 
 Note that `gem` is more of a package manager than `cabal-install` is at the moment. In particular it tracks the files that it installs and supports uninstallation. It also supports signing of packages. It has a configuration file to record user preferences like always building documentation or running unit tests.