| 1 |
On Thursday 21 December 2006 18:04, reader@×××××××.com wrote: |
| 2 |
|
| 3 |
> In the event user runs with ~ARCHITECTURE flag set then masking won't |
| 4 |
> do it... right? |
| 5 |
|
| 6 |
Wrong. |
| 7 |
|
| 8 |
Masking says what portage should include as installable. Look inside an |
| 9 |
ebuild and you will see lines like |
| 10 |
|
| 11 |
KEYWORDS="~ppc sparc x86" |
| 12 |
|
| 13 |
That means that this ebuild is OK for unstable ppc, sparc and x86. It's |
| 14 |
also OK for ~sparc and ~x86. So if you run ~arch then you can install |
| 15 |
any unstable package, and you can also install anything in |
| 16 |
package.keywords that's marked ~arch (or blank, as that's how that file |
| 17 |
works) |
| 18 |
|
| 19 |
> So my understanding is that user needs to set something in: |
| 20 |
> /etc/portage/profile/package.provided showing an equal or higher |
| 21 |
> version number than what is available in portage (masked or not). |
| 22 |
> (To maintain users own package) |
| 23 |
|
| 24 |
No, this is completely wrong. Go read the man page - man 5 ebuild |
| 25 |
|
| 26 |
provided is for packages that you have already provided by other means |
| 27 |
that portage. Example - kernels. Some users like to do the kernel |
| 28 |
themselves without any help form portage. But portage insists on |
| 29 |
knowing about your kernel and will want to install one. So with |
| 30 |
package.provided you are essentially saying "Assume this package is |
| 31 |
already there and I have provided it. I'm the user - trust me" |
| 32 |
|
| 33 |
> Assuming I got this much right, is there a better way? |
| 34 |
|
| 35 |
Yes, do it the way portage is designed to work. With overlays (assuming |
| 36 |
we are still on-topic from my original post |
| 37 |
|
| 38 |
> I ask because setting a higher version number might eventually need |
| 39 |
> bumping still higher... or if versioning changes somehow will |
| 40 |
> `higher' not be noticed. |
| 41 |
|
| 42 |
If you want to maintain and use old package-1.0.0 by yourself, and there |
| 43 |
is already package-2.3 in the portage tree, then you need to mask out |
| 44 |
any version greater than your custom ebuild. So, you put this |
| 45 |
in /etc/portage/package.mask: |
| 46 |
|
| 47 |
>package-1.0.0 |
| 48 |
|
| 49 |
Thus, everthing else in the tree is masked out and can't be used by |
| 50 |
portage. the only thing left is the ebuild in your overlay |
| 51 |
in /usr/local/portage |
| 52 |
|
| 53 |
> Looking for a way not to have to check package.provided to make sure |
| 54 |
> versioning is still good. |
| 55 |
|
| 56 |
You need to learn more about portage. Read: |
| 57 |
|
| 58 |
man portage |
| 59 |
man 5 portage |
| 60 |
man ebuild |
| 61 |
man 5 ebuild |
| 62 |
|
| 63 |
All your questions are answered in there. |
| 64 |
|
| 65 |
alan |
| 66 |
|
| 67 |
|
| 68 |
-- |
| 69 |
gentoo-user@g.o mailing list |
Archives