| 1 |
On 06/06/12 13:37, Hinnerk van Bruinehsen wrote: |
| 2 |
> On 06.06.2012 12:25, Nikos Chantziaras wrote: |
| 3 |
>> I wish to build a binary package of glibc-2.14.1-r3. I don't want to |
| 4 |
>> actually install it on my system. Just build a tbz2 for it to use on |
| 5 |
>> another system. Is there a way to do that? Portage aborts when |
| 6 |
>> emerging an older glibc and won't let you proceed, so I can't just |
| 7 |
>> install it normally and them build a binpkg. |
| 8 |
>> |
| 9 |
>> |
| 10 |
> |
| 11 |
> you should be able to use: |
| 12 |
> |
| 13 |
> ebuild<path-to-ebuild>/glibc-2.14.1-r3.ebuild package |
| 14 |
> |
| 15 |
> Quoting the manpage: |
| 16 |
> |
| 17 |
> package |
| 18 |
> This command is a lot like the merge command, except that |
| 19 |
> after fetching, unpacking, com‐ |
| 20 |
> piling and installing, a .tbz2 binary package tarball is |
| 21 |
> created and stored in PKGDIR (see |
| 22 |
> make.conf(5)). |
| 23 |
> |
| 24 |
> You may need to set PKGDIR. |
| 25 |
|
| 26 |
It still aborts with |
| 27 |
|
| 28 |
* Sanity check to keep you from breaking your system: |
| 29 |
* Downgrading glibc is not supported and a sure way to destruction |
| 30 |
* ERROR: sys-libs/glibc-2.14.1-r3 failed (setup phase): |
| 31 |
* aborting to save your system |
| 32 |
|
| 33 |
Is there an override for that? |
Archives