I would like to propose an enhancement bug for portage if it has not been mentioned already. At the moment, one can inject stubs and remove them but not do anything else with them. It should be made possible to do the following. - display all applied stubs - remove all injected stubs - manipulate stubs so that when a newer version of package is released on stable the stub for the older version is removed or the user is notified of it - if a package needs to be installed that is currently stubbed user is notified Here is a script I use for displaying stubs that was published on gentoo-user ML. ---- #!/bin/sh # Display stub injected packages pushd /var/db/pkg > /dev/null for d in */*; do echo $d `ls $d | wc -l` | awk '{ if ($2 <= 2) print $1 }' done popd > /dev/null ---- Many thanks.
why not add your bit of code to qpkg in gentoolkit ...
Hello. Here is some food for thought and an attempt to clarify ambiguity on this subject. There exists emerge, etcat and qpkg with a large degree of overlap between them although latter two are primarily read only. This brings about the question that if portage doesn't assimilate a new feature request being already heavily overloaded and feature rich then which of etcat and qpkg should adopt it? Now, given that qpkg isn't actively maintained and that I find the new etcat utility much more promising I would like to motion the gradual migration of qkpg functionality possibly to eventually deprecate it. This will mean that new feature requests can then be adopted without indecisiveness by etcat. I'd be glad to hear your thoughts.
Is there any intention at all to ever add functionality to manipulate injected stubs into portage? If not, please add that bit of code below to qpkg and close the bug. If you do not wish to add it to qpkg that is also fine. This has been open for a long time without any real feedback. Thanks.
write a patch ...
qpkg feature
Hello. Here is a simpler and quicker way of finding stubs without using awk. ---- for D in /var/db/pkg/*/*; do if [ $(ls "$D" | wc -l) == 1 ]; then echo -e "$D" | cut -d'/' -f5- fi done ---- Sorry I haven't had time to make a patch. Time is so short that I haven't been able to browse qpkg code to write a patch. I will try and do so as soon as time allows.
injected packages dont have a CONTENTS file ... thus we can do it all in bash: for D in /var/db/pkg/*/*; do [ ! -f ${D}/CONTENTS ] && echo ${D/*\/} done
Created attachment 20599 [details, diff] Patch for injected stubs Here is a patch for qpkg to display injected stubs using the most recent suggestion by SpanKY. Do with what you will :) I've used the standard practice of directories in ${BR} and remainder in ${CY} colour. I wasn't sure about conflicting options but I've added an exit in that section so it doesn't do anything else. Thanks.
Created attachment 20600 [details, diff] Minor corrections including comment
Since gentoolkit has been rewritten into gentoolkit-dev I suppose this bug is obsolete now?
I don't really see a need for this and I certainly don't want to encourage the use of --inject unless it's really necessary. Also gentoolkit tools are generally read-only and shouldn't modify the package database.
Genone. What you say makes absolutely no sense whatsoever. I am asking for a way to list all injected packages on a system. First of all, this is 100% read only. It does not modify the package database. Secondly, it does not encourage injection of stubs but if you do have some stubs injected which you have to do sometimes then it lets you list them in order to delete them. Otherwise how are you supposed to know what's injected and what's not. From what you have said it seems you have not read about this bug properly. If you don't like the patches attached please modify to your liking. It's a ridiculously easy task.
> - remove all injected stubs > - manipulate stubs so that when a newer version of package is released on stable > the stub for the older version is removed or the user is notified of it That's read-only ? The summary says "manipulating", doesn't sound like read-only to me too. The listing feature might be useful, if you're _only_ after that feel free to reopen and change the summary accordingly. I'm always looking at the whole bug, not only the last 3 comments. Btw, I'm on dev-portage, no need to CC me.
Sorry my mistake. I actually completely forgot about the write functionality and I think everyone else had too considering how little attention it had received. I'll change it to read only listing of injected stubs. This should simplify this bug a fair bit. And now that qpkg and equery have evolved so considerably and I'm so out of touch and out of time I doubt my patches here are of any use. Considering how easy this is though one of the devs will no doubt whip this up in a couple of minutes. Thanks for clearing this up genone.
portage-2.0.51 deprecates --inject and has a package.provided config file in it's place. If you want to find everything that you have injected so that you can migrate, just look for all dirs in /var/db/pkg that don't have a CONTENTS file.
