new ebuild Reproducible: Always
Created attachment 287233 [details] duply-1.5.5.1.ebuild
Created attachment 287237 [details] duply-1.5.5.1-r1.ebuild same as duply-1.5.5.1.ebuild with useflags for duplicity (see Bug 383881)
1.5.9 is released.
I'm willing to maintain via proxy-maintainer... ;)
(In reply to comment #4) > I'm willing to maintain via proxy-maintainer... ;) I assume that means that your so far written ebuilds work as expected for you?
Created attachment 340712 [details] duply-1.5.9.ebuild new version
(In reply to comment #5) > I assume that means that your so far written ebuilds work as expected for > you? i use my ebuild in our private overlay and on several machines, so: yes ;) ebuild is very simple, no magic anywhere.
(In reply to comment #6) > Created attachment 340712 [details] > duply-1.5.9.ebuild > > new version Emerges fine on ARCH="amd64" and ARCH="arm" and at least `duply --help` and `duply create` work. I think you can safely add ARCH="~arm" to the ebuild, before it gets added to official tree.
Created attachment 345916 [details] duply-1.5.10.ebuild New version.
Created attachment 374698 [details] duply-1.7.3.ebuild Version bump
(In reply to Marcel Pennewiß from comment #10) > Created attachment 374698 [details] > duply-1.7.3.ebuild > > Version bump A few comments - The description must not contain the package name. How about changing that to "A shell frontend for duplicity" (not dot at the end) - Is app-backup/duplicity really a build time dependency? or is it just a runtime one? - in src_install you can replace 'duply' with ${PN} - Why are you installing the INSTALL.txt file? the package is already installed so what useful information could be in that txt file for the user? I suggest to install a ChangeLog and/or README file (if any). - in pkg_postinst() maybe you can benefit from the readme.gentoo.eclass to avoid spamming the log on every build?
(In reply to Markos Chandras from comment #11) > - The description must not contain the package name. How about changing that > to "A shell frontend for duplicity" (not dot at the end) fixed. > - Is app-backup/duplicity really a build time dependency? or is it just a > runtime one? it is a running dependency. fixed. > - in src_install you can replace 'duply' with ${PN} fixed also in Log-Message. > - Why are you installing the INSTALL.txt file? the package is already > installed so what useful information could be in that txt file for the user? > I suggest to install a ChangeLog and/or README file (if any). indeed ;) There's no Changelog in Upstream-Archive. If we'll deliver a Changelog we have to deliver a readme.txt (14.7kb and there's only one for all 1.7.x-versions) with the portage. Otherwise if 1.7.4. will be released, the upstream readme.txt will be changed in 1.7.x-tree and this package will break. that's not good ;) Now there's no Changelog in ebuild/filesdir. > - in pkg_postinst() maybe you can benefit from the readme.gentoo.eclass to > avoid spamming the log on every build? I didn't know about that, nice feature. Added to ebuild.
Created attachment 374828 [details] duply-1.7.3.ebuild
+*duply-1.7.3 (13 Apr 2014) + + 13 Apr 2014; Markos Chandras <hwoarang@gentoo.org> +duply-1.7.3.ebuild, + +metadata.xml: + Initial commit. Bug #383883. Thanks to Marcel Pennewiß <gentoo@pennewiss.de> + who will proxy-maintain it +
