| 1 |
On Nov 19, 2011 6:56 AM, "Neil Bothwick" <neil@××××××××××.uk> wrote: |
| 2 |
> |
| 3 |
> On Sat, 19 Nov 2011 09:38:42 +1100, Paul Colquhoun wrote: |
| 4 |
> |
| 5 |
> > > ... but every "eix-sync && emerge -avuD @world" finds me having to |
| 6 |
> > > re-edit /usr/portage/virtual/dev-manager/dev-manager-0.ebuild, or else |
| 7 |
> > > portage wants to emerge sys-apps/makedev and sys-fs/static-dev |
| 8 |
> > > |
| 9 |
> > > Is there a way to 'force' portage to use the edited |
| 10 |
> > > dev-manager-0.ebuild and not the original version pulled in by |
| 11 |
> > > eix-sync? |
| 12 |
> |
| 13 |
> > You can copy the ebuild to your own private overlay |
| 14 |
> > ( /usr/local/portage ) make your changes there, and bump the version |
| 15 |
> > number slightly. |
| 16 |
> |
| 17 |
> No need to bump the version number, overlays take priority over the |
| 18 |
> standard tree when there are equal version numbers. |
| 19 |
> |
| 20 |
|
| 21 |
I knew I forgot something so simple >.< |
| 22 |
|
| 23 |
Thanks! |
| 24 |
|
| 25 |
Hmmm... so, @waltdnes, you should modify the procedure a bit, there... |
| 26 |
|
| 27 |
Rgds, |
Archives