wxWindows based client for the eDonkey/eMule/lMule network
Created attachment 12505 [details] /net-p2p/xmule/xmule-1.4.0.ebuild
Created attachment 12506 [details, diff] net-p2p/xmule/files/xmule-1.4.0.patch Patch necessary for compiling with modified CFLAGS (xmule tries to force -O0 in configure).
1.5.0 just entered the tree
*** Bug 22508 has been marked as a duplicate of this bug. ***
1) there is no "new package" bug report for 1.5.0 here 2) my patch was not included, so CFLAGS won't work.. and I'm not mentioned in the Changelog ;-( 3) the description "wxWindows based client... " is better than "gpl clone that doesnt suck". 4) --with-wx-config is not needed 5) you only set MAKEOPTS for emake, not configure or install.. are you sure this is safe? I had race problems building but didn't investigate too much, maybe there are races in make install as well?
One more point, from xmule.org: "xMule v1.5.0 available for testing This is a beta release, available for testing purposes only. As of now, it is very unstable." I thought gentoo policy was not to add known unstable software, even to ~x86?
There is no "new package" report here because malverian added 1.5.0 before someone opened a bug. I guess he didn't mention your name because he did the ebuild on his own and didn't see this bug. For the other things like wx-config or ~ masking you need to talk to malverian, who carries about lmule/xmule. The only thing I did is carry about bug #22513. Additionally you may add yourself to the CC list of bug #22513
Created attachment 13052 [details] /net-p2p/xmule/xmule-1.4.0-r1.ebuild Thanks for patch :) and so sorry to late..
I reopened the bug because there are some valid points in your comment
reassigned to malverian
Jung, what is the purpose of the -r1 ebuild? It looks functionally identical to the original?
xmule-1.5.1 was released 2 days ago and the announcement says this may be released as 1.4.1 stable. malverian - could you please take care of this and fix the outstanding issues with xmule ?
I just added xmule-1.5.1 as ~x86 and removed any stable version as currently no version can seriously be called stable. I hope someone with the necessary knowledge - especially about wxGTK - can take care of this in the not-so-distant future.
Created attachment 13499 [details] xmule-1.5.1.ebuild 1.5.1 ebuild with cflags patch attached. Can we please change the description (after all kernel sources doesnt say "unix clone that doesnt suck" ;-)
Created attachment 13500 [details, diff] xmule-1.5.1-cflags.patch
xmule seems to follow a rather fast development --> stable cycle, so if there are no objections my suggestion would be to follow their stable tree and completly keep out their dev releases from the tree. They are not suited for being stable neither do I know wether their dev releases are suited for ~ (although their development releases seem rather usable). An option would be to constantly package.mask their dev releases but I don't really like this one. If there are nor real problems with that I'd like to handle xmule that way following with their next stable release. Again, I am not a hardcode xmule user, so if there are any reasons that would justify their development releases still be in the tree, please speak up.
ok, I finally had some time to clean up xmule. From now on, only their stable series is followed in the tree.
