| 1 |
Michael Higgins wrote: |
| 2 |
> Perl 5.8 is at end-of-life. |
| 3 |
> |
| 4 |
> Gentoo volunteers are *very* (PAINFULLY) slow in getting 5.10 into the |
| 5 |
> official tree. They unfortunately need all the help they can get, since |
| 6 |
> this is a major failure of Gentoo to "keep up" with the upstream |
| 7 |
> developers and (FWIW) other "distros". This isn't news, BTW... |
| 8 |
> |
| 9 |
> Please report the error on b.g.o., so the perl herd (or whoever is |
| 10 |
> really doing the work now) can fix the problem. Also, #gentoo-perl is |
| 11 |
> the only place to get any real help on these gentoo-perl issues... |
| 12 |
> (devolution to IRC "chat" being yet another systemic failure, IMO, but |
| 13 |
> that's the place the folks making these mistakes may communicate with |
| 14 |
> users). |
| 15 |
> |
| 16 |
> Better yet, take the plunge and go on to install 5.10.1 from the |
| 17 |
> perl-experimental overlay (good luck with *that*) and report how you |
| 18 |
> fixed any issues you come across. It's only going to get to be a worse |
| 19 |
> mess unless everyone who is able picks up the slack for these guys. And |
| 20 |
> you will have to upgrade eventually anyway... so why not now? |
| 21 |
> |
| 22 |
> My $.02, not terribly helpful though, I suppose. :( |
| 23 |
|
| 24 |
FWIW I'm also running RT and it's 200 odd Perl module dependencies on |
| 25 |
the same machine. I can assure you that I have no interest in updating |
| 26 |
the whole stack to perl-5.10 and the QA nightmare that will require. |
| 27 |
|
| 28 |
I solved this the old fashioned way after a bit of coffee this morning. |
| 29 |
Still seems like Portage should be smart enough to tell about the |
| 30 |
missing dep if I asked it correctly. |
| 31 |
|
| 32 |
1. created fake perl-5.10 ebuild which was really just renaming |
| 33 |
perl-5.8.8-r2 and commenting out any {$PN} patches so I didn't need to |
| 34 |
make a bunch of fake patch files in files/. This allowed portage to tell |
| 35 |
me what was requiring perl-5.10 instead of bombing out. |
| 36 |
|
| 37 |
2. Figured out that while the virtual/perl packages weren't specifying |
| 38 |
perl 5.10 the actual perl-core were which is why it didn't make sense |
| 39 |
earlier. |
| 40 |
|
| 41 |
3. Doctored up portage.mask to mask the errant virtuals |
| 42 |
>=virtual/perl-Digest-SHA-5.47 |
| 43 |
>=virtual/perl-Test-Harness-3.17 |
| 44 |
|
| 45 |
Thought grumpy thoughts at developers who let packages into ~x86 with |
| 46 |
completely broken deps. Hard mask that crap next time. |
| 47 |
|
| 48 |
4. Add the needed packages in portage.keywords and make it pretty and |
| 49 |
organized. |
| 50 |
|
| 51 |
# bugzilla and deps for bugzilla-3.4.1-r1, added 20090919 |
| 52 |
www-apps/bugzilla |
| 53 |
dev-perl/Daemon-Generic |
| 54 |
dev-perl/DateTime-TimeZone |
| 55 |
dev-perl/Data-ObjectDriver |
| 56 |
dev-perl/File-Flock |
| 57 |
dev-perl/TheSchwartz |
| 58 |
perl-core/Module-Build |
| 59 |
perl-core/Test-Harness |
| 60 |
virtual/perl-Module-Build |
| 61 |
virtual/perl-Test-Harness |
| 62 |
|
| 63 |
And now I've got a fancy new bugzilla. |
| 64 |
|
| 65 |
kashani |
Archives