On Nov 21, 2007 1:47 PM, Xavier <shiningxc@gmail.com> wrote:
On Wed, Nov 21, 2007 at 01:32:33PM -0500, Dale Blount wrote:
I'll just say this - I didn't even know this op existed, and looking at it, I'm still not even all that clear on what it does... looks to be the same functionality as saying 'no' to the "local package is up to date" question.
Are we sure that's what it does? That's not how I read it's description in the man page.
I'm sure that's not what it does. It does as described in the man page, or as I tried to explain a few posts above.
I'm guessing you could use it if you had downloaded a repo locally to a usbkey/cd (think broadband at work/school, dialup at home). You could then change to that directory and do a pacman -F *.pkg.tar.gz to update preexisting packages and not end up installing them all instead.
I see, that's useful in that case indeed. I'm probably lucky I never had to do that. But if you downloaded the whole repo, you will also have the db.tar.gz, right? So you can always extract that, and then use -Su. But that's less nice. /me thinks ..
Make a DB in that case- thats what repo-add is for. Sync repos actually allow you to resolve dependencies anyway. Executive decision has been made- I'm killing this (and a lot of others signed off). I can't think of a use case where creating a sync DB won't solve the problem. Think of it this way- if you want it to stay, you'll have to justify it like you submitted it in a patch. :) -Dan