This is an update to the adodb-4.0.5 ebuild, I removed the stuff about xmlschema. Reproducible: Always Steps to Reproduce:
Created attachment 33328 [details] ebuild for adodb-4.22 This ebuild also changes homepage and download URI.
Created attachment 33331 [details] new ebuild with correct ${S} S=${WORKDIR}/${PN}
New version of ADODB is now 4.2.3
Created attachment 34290 [details] adodb 4.23 ebuild with docs
It's 4.23 and not 4.2.3 right?
Yeh sorry it is 4.23, but i went with what other people had done for the ebuild naming - ive fixed the descriptions above as well.
In this case, where the app version number is 4.23, should the ebuild have that version number as well? Ive added an ebuild that matches the actual ADODB version number now. Ive tested it. It appears to work. If necessary I could maintain this ebuild.
Just saving the ebuild as adodb-4.23.ebuild works
Any chance this might enter portage
saving it as adodb-4.50.ebuild works great too!
About versions... 1.2.3 != 1.23.0 1.9 is not 90% of 2.0, the next release could just as probable be 1.10... in conclusion: 1.2.3 < 1.22 < 1.23
Ah ok, i get the version numbers now! The ebuild works with 4.50 for me too!
i put adodb-4.5.0 in portage. closing. Jay
could you make that 4.50?
lol. done. 4.50 is in portage..