Difference between revisions of "Cane planning"

From IokeWiki
Jump to: navigation, search
(New page: short for hurricane - package management system, like gems - have one or more repositories, and installs either in a system global or a user global location. can also use an application sp...)
 
Line 2: Line 2:
 
- package management system, like gems
 
- package management system, like gems
 
- have one or more repositories, and installs either in a system global or a user global location. can also use an application specific location
 
- have one or more repositories, and installs either in a system global or a user global location. can also use an application specific location
- have hooks for system specific system management tools, so that
+
- have hooks for system specific system management tools, so that useCane("foo") will actually check - and load - from apt-get for example. only if the system specific packaging tools doesn't load it, it will load with the cane mechanism
useCane("foo") will actually check - and load - from apt-get for example. only if the system specific packaging tools doesn't load it, it will load with the cane mechanism
 
 
- when listing, will use system specific tools to find installed versions too
 
- when listing, will use system specific tools to find installed versions too
 
- should be able to use things on classpath inside of jars too
 
- should be able to use things on classpath inside of jars too
 
- should be able to install directly from a git repository, etc.
 
- should be able to install directly from a git repository, etc.
 
   
 
   
a cane can be autoloaded - specified as a configuration thing for the cane
+
a cane can be autoloaded - specified as a configuration thing for the cane
  
 
cane is loaded automatically as part of Ioke.
 
cane is loaded automatically as part of Ioke.

Revision as of 21:01, 26 January 2009

short for hurricane - package management system, like gems - have one or more repositories, and installs either in a system global or a user global location. can also use an application specific location - have hooks for system specific system management tools, so that useCane("foo") will actually check - and load - from apt-get for example. only if the system specific packaging tools doesn't load it, it will load with the cane mechanism - when listing, will use system specific tools to find installed versions too - should be able to use things on classpath inside of jars too - should be able to install directly from a git repository, etc.

a cane can be autoloaded - specified as a configuration thing for the cane

cane is loaded automatically as part of Ioke.