| 1 |
Hey there Beu, |
| 2 |
> 1) Who is it that made some CPAN builds lowercase (module-build, |
| 3 |
> not Module-Build, net-server not Net-Server)? Bad idea. It would |
| 4 |
> be easier (for my system, at least) to leave the names in the |
| 5 |
> CPAN form. |
| 6 |
|
| 7 |
At one point, the power that was wanted all gentoo ebuilds to be lower |
| 8 |
case. for a few months or so, dev-perl wasn't granted its 'grandfather' |
| 9 |
clause in this regard, hence why there are a few lowercase modules (not |
| 10 |
counting the ones that are legitimately lower case, like |
| 11 |
dev-perl/version). the hassle involved in moving an ebuild has warranted |
| 12 |
fixing the ones like module-build tbh. |
| 13 |
|
| 14 |
> 2) Lots of trouble with modules that indicate major versions |
| 15 |
> with 2 digits and minor revisions with four; Module-Build |
| 16 |
> for example: |
| 17 |
> ... |
| 18 |
> Module-Build-0.26 |
| 19 |
> Module-Build-0.2610 |
| 20 |
> Module-Build-0.2611 |
| 21 |
> Module-Build-0.27 |
| 22 |
> ... |
| 23 |
Blame portage, not us. For a while there at least (pretty sure its still |
| 24 |
the case, but who wants to find out the bad way?), portage would get |
| 25 |
confused by the length of the strings in re: the version numbers. Then |
| 26 |
you have modules with _'s and -'s in the middle and it all goes to pot. |
| 27 |
|
| 28 |
> I bypassed this problem by making my ebuild file names as |
| 29 |
> follows: |
| 30 |
> Foo-Bar-1137143770.0.2611.ebuild |
| 31 |
> where 1137143770 is the 'epoch second' date of the tarball. |
| 32 |
> I can then be sure the order is correct and put code |
| 33 |
> in all ebuilds to get rid of the date-seconds: |
| 34 |
> MY_PV=${PV:11} and so on. |
| 35 |
> |
| 36 |
ick |
| 37 |
|
| 38 |
> 3) I pull my tarballs from my local mirror. I am using my |
| 39 |
> apache server to do this via SRC_URI="http://localhost/..." |
| 40 |
> But sometimes the request goes to my defined gentoo mirror |
| 41 |
> anyway. Why? |
| 42 |
because you don't have nomirror in your ebuilds most likely. src_uri is |
| 43 |
used when the mirrors don't have something (or when the mirror is doing |
| 44 |
the nightly fetches) |
| 45 |
|
| 46 |
> 4) How about adding file:/// and rsync:// support for |
| 47 |
> SRC_URI? |
| 48 |
|
| 49 |
not a portage feature, you'd need to court the portage folks on that |
| 50 |
one. |
| 51 |
|
| 52 |
hope this helps - tree's a bit large and around for years, and what with |
| 53 |
me mucking in for 3+ of those years, a lot of things that were required |
| 54 |
and/or a good idea at the time we're just plain ol' stuck with now |
Archives