Hi, I created an overlay to install pikdev-1.0.0 and all went fine. Is it possible to add this version in the main portage tree? Thank you, Jean-Marc Reproducible: Always Actual Results: dev-embedded/pikdev-0.9.2.1 available in main portage tree Expected Results: dev-embedded/pikdev-1.0.0 available in main portage tree
pikdev-1.1.0 is out
(In reply to comment #0) > Hi, > > I created an overlay to install pikdev-1.0.0 and all went fine. Is it possible > to add this version in the main portage tree? > > Thank you, > Jean-Marc > > Reproducible: Always > > Actual Results: > dev-embedded/pikdev-0.9.2.1 available in main portage tree > > Expected Results: > dev-embedded/pikdev-1.0.0 available in main portage tree > Can you post your ebuild as attachment. I try to install 1.0.0 and 1.1.0 with my ebuild, but it always fails
Created attachment 193597 [details] pikdev-1.0.0.ebuild Hi, ebuild for 1.0.0 attached.
Created attachment 193799 [details] pikdev-1.1.0.ebuild I'll investigate the official ebuild howto to see if I can commit thos ebuilds to the cvs tree, that would be the first time for me.
It seems one need to be a developer to cvs commit or get new ebuild in portage tree, and I'm not a developper. I'll send a message to the gentoo-dev list
Hi, you might like to look into project sunrise as a way of getting your ebuild seen by more people. For more information, please have a read of http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq...
(In reply to comment #5) > It seems one need to be a developer to cvs commit or get new ebuild in portage > tree, and I'm not a developper. > > I'll send a message to the gentoo-dev list > (In reply to comment #4) > Created an attachment (id=193799) [edit] > pikdev-1.1.0.ebuild > > I'll investigate the official ebuild howto to see if I can commit thos ebuilds > to the cvs tree, that would be the first time for me. > tank's for your ebuilds, but in my system, ~x86_64, it not compile. I'll try resolve the problems if i can. i use a
robbat2, you committed the initial version of this pkg. Are you still maintaining it or should it be moved to maintainer-wanted@ ? TIA.
(In reply to comment #8) > robbat2, you committed the initial version of this pkg. Are you still > maintaining it or should it be moved to maintainer-wanted@ ? TIA. Do we really have to move it to maintainer wanted if robbat2 doesn't care about it anymore ? I don't use it and I'm not a kde user, but I bumped it a couple times I believe and was thinking doing that again. The old ebuild worked but it could use some polishing with docs for example. In case I ended up not fixing this I would still simply version bump-it. However a user has reported it didn't work for amd64 and that I can't test. However if you guys think this thing is not useful/relevant to us anymore we can move it to maintainer wanted. Denis.
I added it before the dev-embedded herd existed, and became part of the dev-embedded team when it formed up. I don't have any PIC hardware anymore to test with (I used the app for some university classes). If the users say it works on with their PIC hardware, sure, go ahead and bump it.
1.0 works, but didn't test 1.1
Created attachment 196199 [details] Ebuild for pikdev-1.1.0 Ebuild including dependence for pk2cmd, you have to unmask pk2cmd though. Compiles fine on x86 satble arch. Not tested yet
(In reply to comment #12) > Created an attachment (id=196199) [edit] > Ebuild for pikdev-1.1.0 > > Ebuild including dependence for pk2cmd, you have to unmask pk2cmd though. > Compiles fine on x86 satble arch. > Not tested yet > In ~x86_64 the compilation fail, i tnhink this is related to kde. there is the log: /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.3/../../../../x86_64-pc-linux-gnu/bin/ld: warning: libkdecore.so.5, needed by /usr/lib64/libktexteditor.so, may conflict with libkdecore.so.4 KBEditor.o: In function `KBEditor::slotPrintDialog()': KBEditor.cpp:(.text+0x531): undefined reference to `KTextEditor::printInterface(KTextEditor::Document*)' collect2: ld returned 1 exit status
Tested succesfully Pikdev-1.1.0 compiled with above ebuild together with pk2cmd from portage tree.
This is for kdelibs:3.5 and nothing new depending on it will be introduced to tree. Please open a new report if they ever get kdelibs-4 port out.
Jean-Marc Beaune/tzopik: can you please ask upstream about a kdelibs4 version? While I haven't touched PIC hardware since university, I was given a bunch again this past weekend, and I wouldn't mind the tool being properly available, but I'm not going to let it hold up kdelibs3.5 removal. Reopening to change status.
reso UPSTREAM.
I'll give a try with latest version 1.2.1 and let you know.
Qt4 port has been created and it's back in Portage: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-embedded/pikdev/?hideattic=1
