See http://www.livejournal.com/community/logjam/73089.html
Is there a specific reason we should add this to portage now? If not we should probably mark it as later, seeing that it's a pre-release.
Same reason we include other _pre packages?
Uh, ~arch is not a testing ground for unstable, especially pre-release software. I've added this ebuild to my local overlay, but looking at the Changelog, it's reall not suitable to be included. The tarball doesn't even include your regular README or AUTHORS file.
Also please change the severity. Issues like this should be marked as trivial or enhancement.
i agree with khai here, we don't have the resources to keep track of pre-releases atm. lisa, you're a dev, maybe you could attach an ebuild for us to prove that it works?
4.3.0 is new today. Simply change the latest 4.2.4 to 4.3.0 and commit. I'll keep my hands off since last time I comitted a new version of a Gnome package I wound up maintaining it.
1. SRC_URI needs to be changed 2. the dodoc in src_install() also needs to be updated to reflect the fact that they changed the doc location. I'll provide an ebuild, other then that it seems safe to bump.
Created attachment 25155 [details] correct ebuild for logjam-4.3.0
yeah. i spoke too soon... i suck. :-\
Logjam 4.3.1 released yesterday as per http://www.livejournal.com/community/logjam/75987.html
4.3.2 is now in portage. thanks khai for the changes with the doc locations