Gnome Wave Cleaner A nice soft to do audio restoration: denoise, dehiss, declick and amplify audio files (and covert to mp3/ogg). As this is the first ebuild i submit, the dependencies are surely not correct (i skipped all the gnome part), so it should build corrcetly for gnome users, for the others, i doubt it will...
Created attachment 48215 [details] ebuild for gwc-0.20 (exact version is 0.20-09(alpha))
Created attachment 48550 [details] gwc ebuild (slight changes) I have two changes for this ebuild: The dependency on alsa-driver is bad for 2.6 kernels, do I changed it to alsa-lib. Furthermore, the ebuild works on my iBook, so I added the ~ppc keyword. In my opinion, this ebuild should go to portage as fast as possible!
Sorry, I accidentaly posted this to the wrong bug, it was meant to go to bug 6616. There I found an ebuild for gwc-0.20.09, that looks more advanced than this one. I made some slight changes to THAT ebuild, not to the ebuild originally posted here.
*** Bug 108480 has been marked as a duplicate of this bug. ***
the same ebuild works for gwc-0.21.03
This is a me too request. What needs to happen for this to go in portage? Raphael P.S. We are on 0.21-05 now/
There are a number of issues with this ebuild that would cause it to not be added to portage. 1) It conflicts with net-p2p/ghostwhitecrab. They both install /usr/bin/gwc. Before this is added to portage, a mask needs to be put up on ghostwhitecrab and this package to block the installation of both at the same time. Alternatively, I can modify the ghostwhitecrab package to not install to /usr/bin/gwc. This will, however, require a version bump and previous versions will need to block the install of gwc (the wave cleaner). 2) Much of the versioning regexs can be avoided by using the versionator eclass. Please convert it to that eclass. 3) the "use oss || myconf='${myconf} --without-oss'" syntax should be changed to things like "$(use_with oss)" 4) You sed Makefile.in in the src_compile() function. While that's not tooo bad, it'd be better to go in the src_unpack() function. Not only that, but if you're modifying the Makefile.in, does that also mean we need to rerun the fun autotools? Possibly not, I haven't gotten to look at how this is packaged too much yet. 5) Why do you have to sed the Makefile in src_install? Something seems peculiar about that.
By the way, the ebuild works for the most part; issues 1, 4, and 5 are the ones that really need to be addressed before this can even think about touching portage. Other than that, it's a pretty nice package.
Created attachment 85723 [details] gwc-0.21.05.ebuild gwc-0.21.05.ebuild fixed: - move seds around - use versionator eclass - changed deps
Comment on attachment 85723 [details] gwc-0.21.05.ebuild needs additionl work. I'll repost a better version soon
Created attachment 85743 [details] gwc-0.21.05-r1.ebuild more fixes: - all sed are now in src_unpack()
Created attachment 85744 [details] gwc-0.21.05-r1.ebuild -changed dep =sci-libs/fftw-3*
ebuild also OK for gwc-0.21.08 I have gwc-0.21.08 working for amd64. Can you add the ~amd64 keyword to the next version of the ebuild? >the dependencies are surely not correct (i skipped all the gnome part), >so it should build correctly for gnome users, for the others, i doubt it will... It pulled in 30 ebuilds from gnome on my 'clean' system, so I think it is (probably) OK.
(this is an automated message based on filtering criteria that matched this bug) 'EBUILD' is in the KEYWORDS which should mean that there is a ebuild attached to this bug. This bug is assigned to maintainer-wanted which means that it is not in the main tree. Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Because this is a mass message, we are also asking you to be patient with us. We anticipate a large number of requests in a short time. Thanks, On behalf of the Gentoo Sunrise Team, Jeremy. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq
Created attachment 201368 [details] 0.21-10
Created attachment 201371 [details, diff] Makefile.in.patch
And then it fails to build with ~arch toolchain which is why I stopped there.
Created attachment 271395 [details] gwc-0.21.15.ebuild Ebuild for 0.21-15 release.
Created attachment 271397 [details, diff] Updated makefile.in patch Updated makefile.in patch for 0.21.15
Created attachment 271399 [details, diff] QA patch Patch to fix QA issue (adds a header include for printf)
I was going to add this more recent release to the tree with the updated ebuild and patches I attached since it appears to build fine, but I had problems making the sample wave file load.
