Person:Robin Green

From rPath Wiki

Robin Green

Email: greenrd AT greenrd DOT org
IRC: greenrd
Home page: http://www.greenrd.org/

I have lots of ideas for stuff I want to put in my own distro, but I'm just getting started with rPath Linux and conary right now.

Here's some stuff that I need to file elsewhere on the wiki - when I work out where:

Rough equivalents of Fedora commands

In rPath Linux, conary dependency resolution isn't on by default

The default is distro-dependent. In rPath it's currently off, in Foresight it's on. To turn it on, add to your conaryrc file (`/etc/conaryrc` or `$HOME/.conaryrc` ) the following line:

autoResolve True

Multiple versions of a library (or indeed any trove) can be installed alongside each other!

The old trove will be kept if it is needed by any other trove - but only the required components will be kept. If it is not needed by any other troves, you can pin it to make conary keep it anyway. Make sure to only pin the component(s) you really need, to reduce or eliminate file path collisions.

For dependencies, you may only need the `:lib` component, so there may be no file path collisions. However, if you have a file path collision, you can use `--replace-files` to replace the old version's files with the new version's ones. This may or may not work. A better approach (if you have time) is to rebuild one or both of the versions, changing the recipe to avoid outputting filenames which are the same in both versions (this is the approach I favour, anyway).