| 1 |
Sebastian Günther <samson@××××××××××××××××.de> writes: |
| 2 |
|
| 3 |
> First of all the bug is fixed, and a working patch was there 1 day after |
| 4 |
> the opening. I call this a fast response... |
| 5 |
> |
| 6 |
> For ~x86 this is a working solution, and if you use ~x86: b.g.o *is* the |
| 7 |
> users information system and applying patches should be no problem. |
| 8 |
|
| 9 |
Point taken. |
| 10 |
|
| 11 |
> The problem with glibc is, that you only find issues when you recompile |
| 12 |
> your whole world, which is not needed in most cases. And most of the |
| 13 |
> errors with glibc-2.10.1 result from wrong castings, which is only a |
| 14 |
> compile time issue not a run issue. |
| 15 |
> |
| 16 |
> And all these problems are upstream, so you can patch for yourself in |
| 17 |
> gentoo, but the cleaner solution is to wait for upstream to include the |
| 18 |
> patch there. And release a new version, when they do too... |
| 19 |
|
| 20 |
Thanks for your patience and I learned in an earlier thread one very easy |
| 21 |
way to get things working... |
| 22 |
|
| 23 |
I guess you'd still call it a patch... but not requiring setting up |
| 24 |
your own local portage and producing a patched version. |
| 25 |
|
| 26 |
ebuild /usr/portage/<section>/<pkg>/pkg.ebuild configure |
| 27 |
|
| 28 |
Do necessary manipulations |
| 29 |
|
| 30 |
ebuild /usr/portage/<section>/<pkg>/pkg.ebuild merge |
| 31 |
|
| 32 |
I realize in some cases that would be a recurring chore but I kind of |
| 33 |
doubt it this time. procmail will not likely need updating for some |
| 34 |
time and then like you've suggested portage will have it fixed. |
Archives