0.9.4-23 is out Reproducible: Always Steps to Reproduce:
also, net-p2p/mkdonkey needs to be a dependency i'm working on an ebuild now
Created attachment 47305 [details] proposed ebuild for sancho-bin-0.9.4.23
actually, don't use that one. i'm working on an ebuild that gives an option to USE="java"
Created attachment 47348 [details] MUCH better ebuild for sancho-bin-0.9.4.23 this included support for the java binaries, and fixed a coupla stupid bugs that was in the last one this makes the previous submitted ebuild obsolete
Why must net-p2p/mldonkey be a dependency? I can install Sancho on a machine and control the core which is on another machine.
i suppose it doesn't HAVE to be, but i'm guessing most of the people will be using it on the same machine. anyway, i suppose thats a decision for the dev who commits the ebuild, whenever that may be
I merged the gtk-java version of 0.9.4.25 and immediately noticed some problems. 1) /opt/sancho/lib/libgcj.so.5 is linked to non-existent /opt/sancho/lib/libgcj.so 2) /opt/sancho/lib/libgcj.so.5.0.0 is linked to non-existent /opt/sancho/lib/libgcj.so [1 and 2 are easily fixed by linking them to /usr/lib/libgcj.so or adding a symlink `ln -s /usr/lib/libgcj.so /opt/sancho/lib/libgcj.so`] 3) $ sancho Exception in thread "main" java.lang.NoClassDefFoundError: sancho/core/Sancho I've gotta get it to work before I can add it to portage ;).
Would it be possible to commit the old 0.9.4-21 ebuild for version 0.9.4-25 to portage, so users of the GTK or FOX version can enjoy the new features? Bringing the Java version to work can be done afterwards IMHO.
0.9.4-28 is out
Don't put mldonkey as dep ! I only use sancho/mldonkey because i use them on 2 computers, else i would have use amule or xmule ! Leave it without dep, it's already state in the ebuild you need a core to run sancho !
Also, your ebuild is bug USE="-gtk -gtk2" is trying to get gtk version instead of fox version use gtk && TOOLKIT="gtk" || TOOLKIT="fox" (as it was)
And after testing the 0.9.4.28-fox i still have the bug #69001 :(
Just a question like that. Why is it the binary version that is installed? Why not compile it with gcj? It seems to me it would be what to expect when installing on Gentoo, no?
Today I had a crash with Sancho 0.9.4-21, the latest stable version in Portage. I reported it in Sourceforge and I was asked to use a newer version, which hast my issue fixed. I think althought all the bugs haven't been solved, we cannot prevent newer versions of Sancho come into Portage forever. At least mark them as ~x86 so the user can decide.
0.9.4-33 is out...
0.9.4-37 is out.................
Created attachment 56151 [details] Bumped version to 0.9.4.37 Nothing spectacular, just bumped the version number to 0.9.4.37
New version is out. sancho-0.9.4-38
0.9.4.40 is out, does somebody still care about this package?
"0.9.4.40 is out, does somebody still care about this package?" I care... And btw, .42 is out and mldonkey shouldn't be a dependancy...
0.9.4-43 is out and it would be fine to have it in portage
Created attachment 60348 [details] net-p2p/sancho-bin-0.9.4.43.ebuild Just renamed the .37 ebuild. I only tested the gtk version...
0.9.4-44 is out and it would be fine to have it in portage
0.9.4-45 is out and it would be fine to have it in portage ...
for all the new releases (icluding the .44 and .45) just grab the .43 ebuild and save it into your Portage Overlay. also copy your /usr/portage/net-p2p/sancho-bin/files/sancho.sh to <your overlay>/net-p2p/sancho/files/sancho.sh. "ebuild sancho-bin-x.x.xx.ebuild digest" and emerge away! *note: the .45 fox binary isn't available yet. If you only use the GTK version, touch sancho-0.9.4-45-linux-fox.tar.bz2 in your distfiles directory before creating the digest...
for all the new releases (icluding the .44 and .45) just grab the .43 ebuild and save it into your Portage Overlay. You can rename it to reflect the latest version (atm .45). Also copy your /usr/portage/net-p2p/sancho-bin/files/sancho.sh to <your overlay>/net-p2p/sancho/files/sancho.sh. "ebuild sancho-bin-x.x.xx.ebuild digest" and emerge away! *note: the .45 fox binary isn't available yet. If you only use the GTK version, touch sancho-0.9.4-45-linux-fox.tar.bz2 in your distfiles directory before creating the digest...
0.9.4-47 is out and it would be fine to have it in portage ... Changed severity to major to get some attention ;-) Please don
0.9.4-47 is out and it would be fine to have it in portage ... Changed severity to major to get some attention ;-) Please don´t hurt me for this ;-)
(In reply to comment #27) > 0.9.4-47 is out and it would be fine to have it in portage ... > Changed severity to major to get some attention ;-) > Please don
(In reply to comment #27) > 0.9.4-47 is out and it would be fine to have it in portage ... > Changed severity to major to get some attention ;-) > Please don´t hurt me for this ;-) don't do that i'm gonna ping net-p2p on irc to see if they will let me fix this
Comment on attachment 60348 [details] net-p2p/sancho-bin-0.9.4.43.ebuild submit ebuilds as plaintext, please
0.9.4-50 is out ...
Created attachment 70844 [details] net-p2p/sancho-bin-0.9.4.50.ebuild I removed all references to the FOX version since that one isn't updated since the .44 release... That makes this an GTK-ONLY(!) ebuild...
0.9.4-52 is out, it is enough to rename the 0.9.4-50 ebuild.
Bumped in portage.
