media-video/qdvdauthor-1.5.0 is out since 2008-08-02.
Created attachment 168318 [details] PKGBUILD from Archlinux It's not an ebuild, but maybe it helps building the ebuild. On Archlinux it seems to work.
"export STATIC_FFMPEG=1" should of course be set to 0 on Gentoo.
Created attachment 169680 [details] media-video/qdvdauthor-1.5.0.2 ebuild I updated the qdvdauthor ebuild to version 1.5.0.2 (upstream version "1.5.0-2" tarball, "1.5.0" top level directory within tarball). It builds and seems to run though I can't get either this version or version 1.2 it to build a DVD from my AVI file -- I thought automatic transcoding was supported, and it seems to try, but it fails.
Created attachment 177567 [details] version bump version bump to 1.6.1
Created attachment 177574 [details] fix missing qrender
Are you really sure, that this compiles, when no X is running somewhere in the background? See these bug reports: http://sourceforge.net/tracker/index.php?func=detail&aid=2384143&group_id=98243&atid=620414 http://sourceforge.net/tracker/index.php?func=detail&aid=2394687&group_id=98243&atid=620414
(In reply to comment #6) > Are you really sure, that this compiles, when no X is running somewhere in the > background? > > See these bug reports: > http://sourceforge.net/tracker/index.php?func=detail&aid=2384143&group_id=98243&atid=620414 > http://sourceforge.net/tracker/index.php?func=detail&aid=2394687&group_id=98243&atid=620414 > 1.5.0.2 doesn't of course my 1.6.1/1.6.1-r1 compiles fine without X started (refer to --no-configurator configure option) P.S. Is it to hard to try compile my ebuild without running X? ;]
I can't test your ebuild anymore, because I recently switched to Archlinux. But I tried to compile it the same way as you do in your ebuild, but it failed, because configure couldn't find a running X. Instead of --no-configurator I used -n, which shall be the short form of --no-configurator as ./configure --help says.
1.7.0 is out since 2009-01-18, and since 1.2 crashes on me constantly, it'd be great to get it into portage
Also should mention that there are new templates - though they're now distributed as an rpm instead of a tarball :-(
Created attachment 193588 [details] qdvdauthor-1.8.0-r1.ebuild I add a work in progress ebuild for version 1.8.0. I have done many things from the custom configure script which is used for qdvdauthor manually to make it work and respect basic QA. There is also a bug [1] at sourceforge that requests build system improvements, as the way it is done now is quite suboptimal. [1] http://sourceforge.net/tracker/?func=detail&aid=2790230&group_id=98243&atid=620414
Created attachment 193590 [details, diff] qdvdauthor-1.8.0-r1.diff And one for those who like diffs :)
Created attachment 194946 [details, diff] qdvdauthor-1.8.0-r2.diff Some updates.
Created attachment 196773 [details, diff] qdvdauthor-1.10.0.diff qdvdauthor-1.10.0 is out.
Created attachment 199471 [details, diff] qdvdauthor-1.10.0.diff A tarball including templates is now available for qdvdauthor-1.10.0. I have integrated this into the ebuild via a templates use flag instead of creating an additional package.
Daniel, wouldn't it be better to attach the ebuilds instead of the diffs? It makes more work for you to create the diffs, and the users need to download one ebuild and additionally the diff, and then the users need to apply the patch. If you would attach the complete ebuilds, then you just need to upload one file and the users need to download only one file, which they can save 1:1 into their overlay. And the diffs are much bigger than the ebuilds.
(In reply to comment #16) > Daniel, wouldn't it be better to attach the ebuilds instead of the diffs? Diffs are preferred because it makes it easier to follow the changes. I must confess this makes not much sense in this case as the new ebuild uses a completely different approach compared to the old one. > It makes more work for you to create the diffs, and the users need to download > one ebuild and additionally the diff, and then the users need to apply the > patch. > > If you would attach the complete ebuilds, then you just need to upload one file > and the users need to download only one file, which they can save 1:1 into > their overlay. > > And the diffs are much bigger than the ebuilds. > Well for me it is one command to create the diff :) The user needs to download only the diff. Then he can copy the latest version from the portage tree in his overlay and apply the diff by invoking "patch old.ebuild new.diff". Two commands which are trivial enough I think. As a plus users also learn how to use patch :-)
(In reply to comment #17) > Diffs are preferred because it makes it easier to follow the changes. I must > confess this makes not much sense in this case as the new ebuild uses a > completely different approach compared to the old one. The preferred way for this purpose is not creating patches but changelogs. And in this case it's really much easier to download just one ebuild. And this has nothing to do with the approach of an ebuild. > Well for me it is one command to create the diff :) For you it's one needless and senseless command. For the user it's one needless and senseless additional download and one needless and senseless additional command to patch the ebuild. > The user needs to download only the diff. Then he can copy the latest version > from the portage tree in his overlay and apply the diff by invoking "patch > old.ebuild new.diff". Two commands which are trivial enough I think. No, the user - especially a user, who wants to install qdvdauthor for the first time - needs to download two files (one ebuild and one patch) instead of only one file (one ebuild). A patch for an ebuild costs more time, more work, more bandwidth and more space on the bugzilla. Only downloading one ebuild and saving it 1:1 into an overlay is much more trivial than downloading and applying a patch. And the patch command is by far trivial. And there are many normal users - also on Gentoo - who don't know, what a patch is and what to do with a patch. > As a plus users also learn how to use patch :-) That's not really the sense of downloading an ebuild. And which normal user needs to learn how to use patch? So, please, upload the complete ebuilds instead of patches in the future.
Created attachment 203078 [details, diff] qdvdauthor-1.11.1.diff Call me stubborn or whatever but here is a new diff. Maybe i bump qdvdauthor in the next time so you don't have to worry about the diffs.
+*qdvdauthor-1.11.1 (04 Sep 2009) + + 04 Sep 2009; Pielmeier Daniel <billie@gentoo.org> qdvdauthor-1.2.0.ebuild, + +qdvdauthor-1.11.1.ebuild, metadata.xml: + Version bump. Fixes bugs #255889 and finally #241804. Some small repoman + fixes.
