| 1 |
On Fri, 2003-05-09 at 18:09, Patrick Kursawe wrote: |
| 2 |
> On Fri, May 09, 2003 at 05:48:48PM +0800, Michael Boman wrote: |
| 3 |
> > > 2) Make your own portage mirror (not official) and let the same cron job |
| 4 |
> > > that does the rsync for portage also copy your overlay into the portage |
| 5 |
> > > tree. Use this as the rsync mirror for your other machines. |
| 6 |
> |
| 7 |
> > Let say I have app-shells/bash in my PORTAGE_OVERLAY tree. How would I |
| 8 |
> > go about and make sure that my version of bash is always used, even if a |
| 9 |
> > newer version is distributed from gentoo? |
| 10 |
> |
| 11 |
> Urgh. I thought we were talking about edited/newer files, not about |
| 12 |
> ignoring newer stuff... |
| 13 |
> |
| 14 |
> You could perhaps work around this with a little shell script that |
| 15 |
> scans your overlay and deletes any directory of the original portage tree |
| 16 |
> that is present in the overlay before copying the overlay over the |
| 17 |
> original. |
| 18 |
> |
| 19 |
> Something like: |
| 20 |
> |
| 21 |
> Overlay: |
| 22 |
> foo/bar/bar-1.1.ebuild |
| 23 |
> |
| 24 |
> Original: foo/bar/bar-1.2.ebuild |
| 25 |
> |
| 26 |
> Check: overlay/foo/bar exists. delete original/foo/bar. copy overlay |
| 27 |
> foo/bar original/foo/bar. |
| 28 |
> |
| 29 |
> The more special your wishes become, the more I have the impression that |
| 30 |
> you are asking for trouble and hard to locate bugs :-) |
| 31 |
|
| 32 |
No, not really. The extra ebuilds are for special requirements, ie: most |
| 33 |
people run a software in one way - but I have special requirements and |
| 34 |
need it to do something else/different/more. This can be hacks until |
| 35 |
upstream (either developer or gentoo) accepts patches, or simply just |
| 36 |
hacks. |
| 37 |
|
| 38 |
Best regards |
| 39 |
Michael Boman |
| 40 |
|
| 41 |
-- |
| 42 |
Michael Boman |
| 43 |
Security Architect, SecureCiRT Pte Ltd |
| 44 |
http://www.securecirt.com |
Archives