This is an ebuild for portagedb-0.1.3. Compiled fine on my x86 and works. Also see forum post: <http://forums.gentoo.org/viewtopic.php?t=214547> for more information. I had to hardcode "portdb" in the SRC_URI field since the SourceForge mirror link has "portdb/portagedb-0.1.3". :( If there is a better way around this, please let me know. :) Reproducible: Always Steps to Reproduce:
Created attachment 38399 [details] portagedb-0.1.3 ebuild
as far as i can tell, esearch already fills the capacity portdb tries to fill it's also widely used and has gone through the debugging stages; it's a pretty solid app and the dev hangs out on bugzilla so he fixes things fast for us
Request for reopening this bug since esearch is NOT an adequate subsitute IMO. Anyone that disagrees, please tell me how to get output like this from esearch. * net-www/dillo Available versions: 0.7.3-r7 0.8.0-r4 0.8.0-r5 0.8.1 0.8.2 Installed: 0.8.0-r5 Homepage: http://www.dillo.org/ Description: Lean GTK+-based web browser I'm specifically thinking about the AVAILABLE VERSIONS section. Esearch only prints out LATEST VERSION. Additionally, wontfixing it only becuse a somewhat similar app already exist seems a bit odd. I guess that means 2 of Gnome, KDE and XFCE4 should be removed from portage and lets not even start listing Window Managers, must be 20+ of them...
`etcat -v <package>` (gentoolkit)
That's with etcat, not esearch, requering 2 apps to do the same job. And again, since when is adding a good tool to portage an issue becuse something similar is already present. At least 80% of the apps should be take out if compleatly unique function was a requirement.
because random third party project writes have a habit of disappearing and leaving packages dead if your only gripe with esearch is that it doesnt spit out all the versions i'm sure we could just ask david to add support for it david: what do you think ? could this feature be incorporated into esearch ?
I can't speak for the original bugposter but "Available versions" presented in a good way when searching is probably my most missed feature in emerge (I'm quite amazed this isn't in emerge by default). When I finally found a util that had this on the forums (after having gone through all the app descriptions in the online web-database) I imediately checked if someone has submitted a request to add it and added myself to the cc. So I guess, I don't really care which CLI app has search+available versions as long as at least 1 exsists in portage (so you can find it easily). I don't really need any of the other features of either searchdatabase, so for me (and plausably many other enduser) the optimal solution would be if it was added to the default emerge -s command. Though adding it to esearch would be a resonable solution as well if there's too much red tape involved with adding stuff to emerge. :)
I have been busy during the last few days and had no time to do updates. First: portagedb-0.1.3 contains a stupid mistake which makes it search in descriptions whether you specify 's' or 'S' as a command. A quick fix is to change the declaration "bool searchdesc;" in main.cc to "bool searchdesc=false;". Some free time is in sight and I'll try to implement new things more carefully. It is nice to see that others also use this little tool but I also understand that currently portagedb does not significantly differ to existing programs in the portage tree. That is why pdb is marked as "Stage 1 - Planning" at sf.net. I'm experimenting with some new features and plan to release 0.1.4 during the next days. If you find errors or have a feature request, you can post at the portdb.sf.net site which I check at least every 3 days. Just wanted to let you know that I'm still alive :)
Hi, I already implemented a "verbose" option for esearch, which could also show additional information like all the available versions. It will also show USE-Variables, Masked Versions etc. Please wait for the next version :-)
Re #9 Sounds greate. Let us know when it's out. :)
