There needs to be a dijjer ebuild. Reproducible: Always Steps to Reproduce: 1. emerge dijjer 2. 3. Actual Results: no ebuild found Expected Results: dijjer gets merged
Created attachment 65016 [details] dijjer-117.ebuild (New Package) Ebuild that seems to work for me...file/dijjer next
Created attachment 65017 [details] dijjer (for /etc/init.d/)
Please always assign text/plain. Also I wonder why any developer would have the slightest look at this, when you can't even add a description and url.
"Dijjer is free P2P software that dramatically reduces the bandwidth needed to host large files." It is something like bittorrent, but requires nothing more than a modified url to host files with dijjer (no trackers, etc).
Created attachment 65197 [details] dijjer (for /etc/init.d) Removed working seednode in command, since a working one is now in the source.
Created attachment 65198 [details] dijjer-118.ebuild Using build 118, added ~amd64, now with better ebuild practices :)
Created attachment 65275 [details] dijjer-118.ebuild ${P} != ${PN}... little bugfix
Created attachment 65562 [details] dijjer-118.ebuild Ok, I'll get it right one of these days... fixed yet another dumb bug.
I'm hosting these along with some helpful instructions at http://dijjer.jk3.us/ until this make it to the tree, for anyone who's interested.
Created attachment 83844 [details] dijjer-120.ebuild ebuild for build 120
Created attachment 83845 [details] /etc/init.d/dijjer new /etc/init.d/dijjer... now using java-config to find java binary. (Is this the proper way to do it?)
dijjer-120.ebuild DESCRIPTION="java distibuted web cache" What is this? I find your description in Comment #4 much more self-explainatory: DESCRIPTION="Peer to peer program similar to bittorrent with easy file publishing". I'm not sure it is useful to indicate that it is programmed in Java.
Created attachment 84232 [details] dijjer-120.ebuild good point, updated.
Judging from http://www.gentoo.org/proj/en/java/java-devel.xml it looks like this ebuild could use some updating. I'd give it a shot if nobody else is up for it.
*** Bug 144508 has been marked as a duplicate of this bug. ***
Created attachment 94683 [details] dijjer-120-r1.ebuild What needs to be done to move forward with this package? I'm uploading dijjer-120-r1.ebuild, files/dijjer-pkg-2.confd, and files/dijjer-pkg-2.initd. These use the new java-pkg-2 stuff and move configuration into conf.d/dijjer. They don't replace the existing files since not everyone is using the new Java stuff yet.
Created attachment 94684 [details] files/dijjer-pkg-2.initd
Created attachment 94685 [details] files/dijjer-pkg-2.confd
Comment on attachment 94683 [details] dijjer-120-r1.ebuild I'm adding a script to prepend the Dijjer node to the list of GENTOO_MIRRORS in /etc/make.conf
Created attachment 95128 [details] dijjer-120-r1.ebuild
Created attachment 95129 [details] files/dijjer-config
(In reply to comment #6) > Created an attachment (id=65198) [edit] > dijjer-118.ebuild > > Using build 118, added ~amd64, now with better ebuild practices :) Jay, did you actually test under amd64?
(In reply to comment #20) > Created an attachment (id=95128) [edit] > dijjer-120-r1.ebuild > exeinto /etc/init.d newexe ${FILESDIR}/dijjer-pkg-2.initd dijjer insinto /etc/conf.d newins ${FILESDIR}/dijjer-pkg-2.confd dijjer You should use newinitd and newconfd here exeinto /usr/bin newexe ${FILESDIR}/dijjer-config dijjer-config dobin takes care of this in one line if [ ! -d ${DIJJER_DATADIR} ] then mkdir ${DIJJER_DATADIR} fi chown -R dijjer:nobody ${DIJJER_DATADIR} chmod -R 700 ${DIJJER_DATADIR} Instead of doing this in the init script, you could consider moving this logic to the ebuild. Of course there is the point of having the control of moving the directory somewhere else. start-stop-daemon --start --exec /usr/bin/dijjer --chuid dijjer \ --background --make-pidfile --pidfile ${DIJJER_PIDFILE} -- ${ARGS} start-stop-daemon can't be directly used on wrapper scripts. I don't remember the specifics here on how to correct it. Uberlord knows better. #Uncomment to specify seednodes in address:port format, separated by spaces DIJJER_SEEDNODES='dijjer.volkmesh.net:9114' ^ Should probably be commented Please note that these were comments by just looking at the files. I haven't actually tested it in practise.
Removing EBUILD from keywords until changes in Comment #23 are implemented. thx
(In reply to comment #24) > Removing EBUILD from keywords until changes in Comment #23 are implemented. thx > Wow, this bug is still around? As far as I know, dijjer is a completely dead project. I'd suggest cosing this bug one way or another. WONT FIX is entirely reasonable as there's unlikely to be anyone willing to do any maintenance even just to get the ebuild shaped up.
Agreed. dijjer is dead for now. Marked WONTFIX.
