| 1 |
On 07/09/2017 12:59 PM, Ста Деюс wrote: |
| 2 |
> Hi. |
| 3 |
> |
| 4 |
> |
| 5 |
> Is it possible to compile/install a testing version of a package w/ its |
| 6 |
> dependencies on a stable OS installation? -- I mean, if a have stable |
| 7 |
> installation of whole the system, can i compile and install a testing |
| 8 |
> version of single package and the packages this single package depends |
| 9 |
> on? |
| 10 |
> |
| 11 |
> |
| 12 |
> Thank you for your time, |
| 13 |
> Sthu. |
| 14 |
> |
| 15 |
|
| 16 |
Yep, it can be done! Fairly easily, too: |
| 17 |
|
| 18 |
A good way to do this (imo) is to create binary packages for any |
| 19 |
packages you're going to be upgrading *BEFORE* attempting to install |
| 20 |
from ~arch. This gives you a "get out of jail free" card to play around |
| 21 |
with the ~arch package(s) and revert (by reinstalling the binary |
| 22 |
package) in case it was a bad decision to upgrade. It's a good idea to |
| 23 |
do this for any packages that could seriously break your system, like |
| 24 |
toolchains. |
| 25 |
|
| 26 |
Check out `man 5 make.conf`, `man quickpkg`, and `man |
| 27 |
package.accept_keywords` for more information. |
| 28 |
|
| 29 |
In short: |
| 30 |
|
| 31 |
* Set '~arch' or equivalent in p.accept_keywords for the package(s) |
| 32 |
you're upgrading. |
| 33 |
* Check `emerge -pv cat/foo` output, where cat/foo is the package being |
| 34 |
upgraded. |
| 35 |
* Run `quickpkg` on the packages that you care about not breaking, |
| 36 |
especially anything close to the toolchain. Be sure to read the |
| 37 |
manual first, as usual. :P |
| 38 |
* Double-check to make sure the binary packages are available. They'll |
| 39 |
be in $PKGDIR, defined in /etc/portage/make.conf. |
| 40 |
* Run your emerge magic to upgrade. |
| 41 |
* ??? |
| 42 |
* Profit! |
| 43 |
|
| 44 |
-- |
| 45 |
Daniel Campbell - Gentoo Developer |
| 46 |
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
| 47 |
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |
Archives