| 1 |
Op maandag 9 januari 2006 22:35, schreef Beau E. Cox: |
| 2 |
> On Monday 09 January 2006 11:15 am, Holly Bostick wrote: |
| 3 |
> > Beau E. Cox schreef: |
| 4 |
> > > Hi - |
| 5 |
> > > |
| 6 |
> > > I'm working on a series of ebuilds for the more esoteric CPAN modules |
| 7 |
> > > that I use. In the Gentoo Developer Handbook there is a statement |
| 8 |
> > > about PORTDIR_OVERLAY: |
| 9 |
> > > |
| 10 |
> > > "In that directory, you must use the same structure (and categories) |
| 11 |
> > > as in /usr/portage." |
| 12 |
> > > |
| 13 |
> > > OK. But I really want to make a new category, i.e. 'cpan'; ( tried |
| 14 |
> > > it, doesn't work ). Is there a way to 'fake out' portage into using a |
| 15 |
> > > new category without breaking everything? |
| 16 |
> > |
| 17 |
> > Question #1-- what's wrong with dev-perl, where all the other modules |
| 18 |
> > are (and then naming the modules cpan-whatever, I suppose)? |
| 19 |
> |
| 20 |
> Answer #1-- I am doing that now. It's OK, but I sometimes have the |
| 21 |
> same module that is already in dev-perl; I would like to be distinct |
| 22 |
> with my config/version/mods/patches/etc. |
| 23 |
> |
| 24 |
<..> |
| 25 |
|
| 26 |
Simple give your ebuild a higher version number. Append e.g. r1 or .1 to the |
| 27 |
version number. Like that, portage will also automatically pick it up. |
| 28 |
|
| 29 |
Jan |
Archives