Created attachment 336416 [details] passwordsafe-0.9_beta.ebuild I'm working on an ebuild for Password Safe, a Popular easy-to-use and secure password manager (https://sourceforge.net/projects/passwordsafe/) with the help of the Gentoo Sunrise folks. Suggested category/package is app-crypt/passwordsafe. Provisional (already reviewed) ebuild is attached.
Created attachment 336418 [details, diff] Patch that is applied by the ebuild.
Comment on attachment 336416 [details] passwordsafe-0.9_beta.ebuild >x11-libs/wxGTK Do this work with ANY wxGTK(both 2.8 and 2.9)? 2.9 is masked for now, but packages, that i have usually seen works only with one wxGTK branch(2.8 or 2.9) but not both. Please check and correct dependency if it is needed
Thanks for the suggestion. A quick search of the tree shows that almost every wxGTK dependency includes the slot. I hadn't checked prior to your post, but this program compiles and appears to operate properly when built against either 2.8 or 2.9, so I'm going to leave the ebuild alone for now.
I updated the ebuild to version 0.95 (actually wrote it myself, found this and merged them). Additional features are existing i18n, slotted wxGTK to version 3.0 and yubikey support (which compiles and runs, but is untested due to the lack of hardware). Sadly the build requires c++11 features. The ebuild itself is not yet reviewed, espacially the c++11 checking code is something I'm not sure about. Maybe it would be better to use -std=c++0x. It enables the same features, but is available in earlier gcc versions. If some of the devs here would maintain the package I would be thankfull, otherwise I would volunteer to proxy-maintain that package.
Created attachment 393886 [details] passwordsafe ebuild
Created attachment 399910 [details] passwordsafe-0.95.1_beta.ebuild I tried to improve it. The main differences are that it uses the wxwidgets eclass, it strips unsafe flags because they made it segfault on my system and removed the "cp src/ui/wxWidgets/version.in src/ui/wxWidgets/version.h" because I had no problem so I think it's not needed any more.
Just declare here you're willing to be a proxy maintainer of this package once committed to portage either under my supervision personally and / or under the authority of the proxy-maint project. Once done, I shall get the ebuild into my local system and runtest.
Created attachment 400808 [details] passwordsafe-0.95.1.ebuild I would proxy-maintain passwordsafe, since I use it regulary. I already proxy-maintain some ebuilds, which are reviewed and commited via xmw, who is a member of proxy-maint and I know him personally. I've added the ebuild which I currently use personally, which is mostly the ebuild by Simone Scanzoni. I've dropped the _beta in PV, because all Linux releases are currently called beta, but that has nothing to do with the versioning. I currently have the package under app-admin/, but that's mostly because keepass and keepassx are under app-admin/.
Version 0.96 is out. I just renamed my ebuild and it worked fine.
0.97 is out, I'll have a look at this (hopefully) later today. @Hendrik, still interested to proxy maintain this?
I can proxy-maintain it, even thoug I have switched to keepass in the last time. I am still keeping a recent version of passwordsafe in my overlay and my version check is reminds me that a new version is out since a few days. Just haven't had the time to check it yet. I'm already proxy-maintaining several packages via xmw who I know personally. If it's fine by you I would do it the same way for passwordsafe
oooh I missed Hendrik v. Raven 2015-04-08 08:09:20 UTC
What we need here is a fully update ebuild for 0.97, In the ines supplied we have MY_P="pwsafe-${PV}BETA" DESCRIPTION="Password manager with wxGTK based frontend" HOMEPAGE="http://pwsafe.org/" SRC_URI="mirror://sourceforge/${PN}/${MY_P}-src.tgz" which are giving us unwanted beta versions. All deps and config options need be reviewed and updated as required. Then we can get this started.
I added a slightly updated variant to my overlay for testing: https://gitweb.gentoo.org/dev/mrueg.git/commit/?id=b139b20520f9a194501c4894f5d9dd9429a08b70
After some absence I now would take care of the package if no one else volunteers. My Yubikeys have arrived recently and I can confirm that yubikey support is working. I used the beta builds for my overlay because I assumed they are different in some way. But after diffing 0.97-beta and 3.37 the only difference is that the beta enforces -fPIC and the 3.37 has a Changelog, a windows version.h and a .pot file. Since -fPIC should be handled by the package manager there is no reason to use the beta builds. But on the other side the ebuild should work fine without any major changes for the regular releases.
Sorry for the delay. Are you saying you'd like to be proxy maintainer of this either under direction of a single developer or the proxy-maintainers project?
yes I would proxy-maintain this package
@Hendrik: Probably the easiest way to get this to the tree is to join #gentoo-proxy-maint on freenode irc and talk to idella4 or me (mrueg). Thanks!
@Hendrick: ping, are you still interested in proxied maintaining?
Yes I am. Just haven't found the time to visit #proxy-maint for a discussion on which version to use. As far as I see that there's no difference between the linux-beta tree and the main windows tree. Both are the same branch in the repo, the only difference is the point at which things are marked as a release. Meaning not every time main gets a release beta gets a release and vice-versa. I would tend to package the beta tree (currently 0.97), because it is more consistent with the website and other distros.
(In reply to Hendrik v. Raven from comment #20) > Yes I am. Just haven't found the time to visit #proxy-maint for a discussion > on which version to use. > As far as I see that there's no difference between the linux-beta tree and > the main windows tree. Both are the same branch in the repo, the only > difference is the point at which things are marked as a release. Meaning not > every time main gets a release beta gets a release and vice-versa. I would > tend to package the beta tree (currently 0.97), because it is more > consistent with the website and other distros. I would suggest to package 0.96 because there is a regression in 0.97 which breaks autotyping in some cases: http://sourceforge.net/p/passwordsafe/bugs/1281/
Rewrote ebuild to use cmake-utils https://gitweb.gentoo.org/dev/mrueg.git/tree/app-admin/passwordsafe/passwordsafe-0.98_beta.ebuild
As I haven't heard back, I'll add myself as the maintainer and add it to the tree. commit 13ace59cf42bc79837fef1daf078f6946b123b2f Author: Manuel Rüger <mrueg@gentoo.org> Date: Sun Mar 6 16:17:32 2016 +0100 app-admin/passwordsafe: Initial version Gentoo-Bug: #453458 Package-Manager: portage-2.2.27
