a renamed copy of a non-_pre-ebuild works fine Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 14623 [details] k3b-i18n-0.9.ebuild
Created attachment 14650 [details] new k3b ebuild Complete ebuild for k3b 0.9
Created attachment 14651 [details] new k3b ebuild Complete ebuild for k3b 0.9 (Resubmited cause of Software 400 error)
k3b 0.9 is in portage, what should the i18n thing do?
How about adding the i18n source package to SRC_URI if LINGUAS is defined?
i think `use nls` is the way to go atm. btw. 0.10 is out ;)
*** Bug 31040 has been marked as a duplicate of this bug. ***
*** Bug 18117 has been marked as a duplicate of this bug. ***
The ebuild attached in Bug 31040 isn't good, because the dependencies are not updated (at least cdrtools >= 2.01a17, sox and dvd+rw-tools has to be added). It does not make sense to me, to write the ebuild, because I don't have a dvd toaster and I won't attach an untested ebuild.
What about posting so that people can test? That's the purpose of these pages and my original intention. If you don't like the ebuild, you're most welcome to edit it or post a new one, that's why I posted a first draft in the first place.
Adding something: dvd+rw-tools is not a dependency (is not needed to run k3b), it's an optional package. The cdrtools >= 2.01a17 thing is necessary only for some features (I don't have it and K3b works fine). By the way both packages are masked, so it makes little sense to make a dependency out of them. I tried to access some features of K3b, which I knew I could not use because I had not the proper packages installed, and k3b responded telling me which package I was missing. I believe we should enforce as few dependencies as possible to avoid an overload. However I'll se if I can write a better one soon.
An attempt at 0.10 is in portage. Please test it out and make sure it works for you.
Hi, I would like to suggest to change the line app-cdr/dvd+rw-tools in: dvdr? ( app-cdr/dvd+rw-tools ) adding of course dvdr in the IUSE. This way k3b 0.10 can still be emerged without masked dependencies as dvd+rm-tools, and people without a dvd burner won't lose their time and space on something they won't use. Cheers, -Federico
Hi, the 0.10 in portage compiles fine on my machine. It blanked fine a CDRW, and burned back on it an image. Looks alright. I hate to repeat myself over and over and sound like an PITA, but what about including that k3b-i18n stuff in portage tree? We have it for kde, is there any reason to keep it out? Cheers, -Federico
-> Bug 32113