Re: proposed pkg_delete change
On Mon, 8 May 2000, Mike Pritchard wrote: On Mon, May 08, 2000 at 02:10:28AM -0400, Kenneth Wayne Culver wrote: I have a suggestion for pkg_delete: Very often when I'm deleting a package (such as kde, after testing the port) I want to delete that package, and all it's dependancies; instead of going around looking for the dependancies, I think it would be a nice idea to add an option to pkg_delete to automatically delete all dependancies that aren't currently used by anything else. If nobody is interested in doing this, I can do it when I have some spare time (finals here at school). And then submit patches. That would have saved me a *lot* of time about a month ago when I went and weeded out all of my packages when my /usr filled up. I basically did what you are proposing by hand and it took forever. e.g. pkg_delete some_package - oops, it depends on pkg_xxx, delete that, oops, it depends on pkg_xxx2, and so on, when in reality that only reason any of those additional packages were installed were for the original package. I just go to /var/db/pkg and type 'pkg_delete kde*' a few times. After a while they all get deleted. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 20 8442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proposed pkg_delete change
Yeah, but some ports and projects don't have the same beginning to their names which prompted me to make my suggestion. = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Tue, 9 May 2000, Doug Rabson wrote: On Mon, 8 May 2000, Mike Pritchard wrote: On Mon, May 08, 2000 at 02:10:28AM -0400, Kenneth Wayne Culver wrote: I have a suggestion for pkg_delete: Very often when I'm deleting a package (such as kde, after testing the port) I want to delete that package, and all it's dependancies; instead of going around looking for the dependancies, I think it would be a nice idea to add an option to pkg_delete to automatically delete all dependancies that aren't currently used by anything else. If nobody is interested in doing this, I can do it when I have some spare time (finals here at school). And then submit patches. That would have saved me a *lot* of time about a month ago when I went and weeded out all of my packages when my /usr filled up. I basically did what you are proposing by hand and it took forever. e.g. pkg_delete some_package - oops, it depends on pkg_xxx, delete that, oops, it depends on pkg_xxx2, and so on, when in reality that only reason any of those additional packages were installed were for the original package. I just go to /var/db/pkg and type 'pkg_delete kde*' a few times. After a while they all get deleted. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd.Phone: +44 20 8442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proposed pkg_delete change
I have a suggestion for pkg_delete: Very often when I'm deleting a package (such as kde, after testing the port) I want to delete that package, and all it's dependancies; instead of going around looking for the dependancies, I think it would be a nice idea to add an option to pkg_delete to automatically delete all dependancies that aren't currently used by anything else. That would be cool, yes. If you've got the time to do it, I think it would be well-worth the effort. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proposed pkg_delete change
On Mon, May 08, 2000 at 02:10:28AM -0400, Kenneth Wayne Culver wrote: I have a suggestion for pkg_delete: Very often when I'm deleting a package (such as kde, after testing the port) I want to delete that package, and all it's dependancies; instead of going around looking for the dependancies, I think it would be a nice idea to add an option to pkg_delete to automatically delete all dependancies that aren't currently used by anything else. If nobody is interested in doing this, I can do it when I have some spare time (finals here at school). And then submit patches. That would have saved me a *lot* of time about a month ago when I went and weeded out all of my packages when my /usr filled up. I basically did what you are proposing by hand and it took forever. e.g. pkg_delete some_package - oops, it depends on pkg_xxx, delete that, oops, it depends on pkg_xxx2, and so on, when in reality that only reason any of those additional packages were installed were for the original package. -Mike -- Mike Pritchard [EMAIL PROTECTED] or [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proposed pkg_delete change
* From: Kenneth Wayne Culver [EMAIL PROTECTED] * dependancies, I think it would be a nice idea to add an option to * pkg_delete to automatically delete all dependancies that aren't currently * used by anything else. If nobody is interested in doing this, I can do it Be careful about that "aren't currently used by anything else" part. If you already had a port A installed, and then later installed B (which just happens to depend on A), you could get A erased when you erase B. You probably need to change pkg_add too, so that it will note somewhere on A's dependency list that it was installed by which port, and let pkg_delete check it. It usually goes like this: @ install B, pkg_add installs A too, and mark A that it was "installed by B" @ deinstall B, pkg_delete checks A, finds the mark and deletes it too While, if you had installed A beforehand, it will be like: @ install A (...few months pass...) @ install B, nothing special happens re the flag @ deinstall B, pkg_delete checks A and doesn't find the flag, so doesn't delete it You can also add a flag to pkg_delete to override said check in case you know you installed A just for the purpose of installing B. If you come up with the file format and patches to pkg_*, I'll modify bsd.port.mk so it will DTRT on dependencies installed by "make install". Satoshi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proposed pkg_delete change
On Mon, May 08, 2000 at 02:30:59AM -0700, Jordan K. Hubbard wrote: (such as kde, after testing the port) I want to delete that package, and all it's dependancies; instead of going around looking for the [...] That would be cool, yes. If you've got the time to do it, I think it would be well-worth the effort. Even cooler: A tree-like drawing of the dependency graph, allowing me to do right-click--toggle keep/erase for given port left-click--select port and all dependencies for erasure (excluding dependencies shared by another port not previously left-clicked) -- Signature withheld by request of author. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proposed pkg_delete change
I have a suggestion for pkg_delete: Very often when I'm deleting a package (such as kde, after testing the port) I want to delete that package, and all it's dependancies; instead of going around looking for the dependancies, I think it would be a nice idea to add an option to pkg_delete to automatically delete all dependancies that aren't currently used by anything else. That would be cool, yes. If you've got the time to do it, I think it would be well-worth the effort. Alright, I'll get on it probably in 2 weeks when finals are over. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proposed pkg_delete change
On 8 May 2000, Satoshi - Ports Wraith - Asami wrote: Be careful about that "aren't currently used by anything else" part. If you already had a port A installed, and then later installed B (which just happens to depend on A), you could get A erased when you erase B. Have a -n mode (-nothing) which prints a list of actions it would take so you can review. You probably need to change pkg_add too, so that it will note somewhere on A's dependency list that it was installed by which port, and let pkg_delete check it. This could be done with an extra binary field in +REQUIRED_BY showing whether the package was installed by a parent. pkg_delete would recursively remove it if 1) There was only a single +REQUIRED_BY entry, and 2) The parent package bit is set. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
