| 1 |
Jason Stubbs wrote: |
| 2 |
> Only by modifying every ebuild that has a virtual/x11 dependency. The atom |
| 3 |
> "virtual/x11" cannot be limited to specific versions on its own with old |
| 4 |
> style virtuals. |
| 5 |
|
| 6 |
Is that so? I guess this must be wrong, then: |
| 7 |
|
| 8 |
/usr/portage/profiles/base/virtuals:# Only have this for >=pam-0.78, as |
| 9 |
we want to make use of the 'include' |
| 10 |
/usr/portage/profiles/base/virtuals:virtual/pam |
| 11 |
>=sys-libs/pam-0.78 |
| 12 |
|
| 13 |
> The premise for not doing this is that packages will never be fixed, right? |
| 14 |
> Why not make the modular X provide virtual/x11 and just institute a policy |
| 15 |
> that no new packages can go into stable with a virtual/x11 dependency? It |
| 16 |
> could even be easily enforcable if necessary. |
| 17 |
|
| 18 |
How does that fix the stale, unmaintained here and upstream apps that |
| 19 |
are in stable now and have no ~arch ebuilds? |
| 20 |
|
| 21 |
Thanks, |
| 22 |
Donnie |
Archives