[Yum-devel] Such pretty, pretty crack

[Panu Matilainen]

On Mon, 2005-01-31 at 03:48 -0500, seth vidal wrote:
> hi all,
>  So apparently I was on drugs this weekend. I can only assume this b/c I
> implemented some things which could, very likely, fall into such a
> category.
> 
>  1. yum resolvedep /usr/bin/foo
>    this will search the repos for something that resolves that dep
>    ditto for: yum resolvedep "foo > 1.1" and yum resolvedep bar
>  2. yum install /some/misc/file 
>     - using the above function internally it allows you to do file-path 
>       installs. I think this is a crack command line arg item but there 
>       it is. No, it doesn't support globbing, no, i'm not interested in 
>       having it support globbing. :)

I fail to see why you think of this as crack. :) It's an incredibly
useful thing to have at times - for example you remember the command but
not the package name. My favorite example of this is "uudecode", I never
remember where it comes from so:
[root at chip ~]# apt-get install /usr/bin/uudecode
Reading Package Lists... Done
Building Dependency Tree... Done
Selecting sharutils for '/usr/bin/uudecode'
The following extra packages will be installed:
   sharutils (4.2.1-22)

It might not be the most frequently used feature but that doesn't mean
it's not useful.

>  
> Now for the special, special crack, that really needs some more cleaning
> up:
>   yum shell
> 
> yum shell will dump you out at a prompt (after reading in the rpmdb and
> setting up potential transaction set stuff)
> then all the normal yum commands will function:

Heh, cool. Shell-mode is nice when you expect to do several operations,
eg when searching packages and spring cleaning of systems (meaning
finding and throwing out useless rpms) since you avoid the startup time
between operations. Apt has shell-mode as well but somehow nobody seems
to be using it so dunno if it's that useful feature afterall :) But if
it doesn't cost you much in the way of maintenance ... well, why not?
	
	- Panu -