Dieter Plaetinck wrote:
Jason Chu wrote:
On Fri, Nov 21, 2008 at 9:05 AM, Loui Chang <[EMAIL PROTECTED]> wrote:
On Fri, Nov 21, 2008 at 05:36:17PM +0100, Pierre Schmitz wrote:
On Fri, 21 Nov 2008 09:52:45 -0600, "Aaron Griffin"
<[EMAIL PROTECTED]> wrote:
On Fri, Nov 21, 2008 at 8:01 AM, Pierre Schmitz <[EMAIL PROTECTED]>
wrote:
Hi,
the recent version of pacman (repo-add) stores information about
optdepends
in the db files. It would be great if we could regenerate the db-files
for
all repos.
Do you think that the following might work?
rm *.db.tar.gz
repo-add $repo.db.tar.gz *.pkg.tar.gz
Pierre
PS: I could do it for core, extra and testing (community needs to be
done
by someone else).
That sounds fine, but can you mv the old db rather than rm it?
OK, I ust did it. The old db files are moved to *~. I hope I did not break
too much. Could someone with access do the same with the community repo?
How useful is it to add optdepends in the repo DB? They aren't
necessarily critical to a package's installation or operation. When the
package is installed the user is informed about them anyways. That's the
only time I can think of that optdepends become useful.
What about pacman -Si?
Pacman -Si or -Ss says "Optional Deps : None", even if a package has
them. Coincidentally I was confused by this yesterday. See
http://bbs.archlinux.org/viewtopic.php?id=59374
Loui, imho if it doesn't "cost" anything to show more info about a
package without needing to install it, it can be nothing but useful,
even if it's for just a few users/use cases.
Never mind about '-Ss'..
Btw: I have a use case: If the user has optdeps installed for a package,
and he removes that package, he will probably want to check if he
installed any optdepends that can be removed as well. You can/should
only remove optdeps after successfully removing the main package, eg you
need pacman -Si. (okay you could do pacman -Qi, 'remember' the
optdepends, remove, and then check if the optdepends are on your system
, but -Si is more KISS :-)
