Mailinglist Archive: zypp-devel (227 mails)
| < Previous | Next > |
Re: [zypp-devel] selecting patches by issue
- From: Martin Vidner <mvidner@xxxxxxx>
- Date: Mon, 14 Apr 2008 14:25:47 +0200
- Message-id: <20080414122547.GA6715@xxxxxxxxxxxxxxxx>
On Mon, Apr 14, 2008 at 02:04:55PM +0200, josef reidiner wrote:
"Uninstall all packages with careless maintainers" ;-)
zypper rm `zypper se --search-descriptions teh`
zypper in -t patch `zypper se -d -t patch BNC#38810`
Well OK, we would need to remove the formatting from the search
output...
It is cleaner than having to search the free form description.
Now that I think of it, having the patch metadata in a form
different from Provides seems wrong, because that only forces you to
write new code for what is served by Provides better.
--
Martin Vidner, YaST developer
http://en.opensuse.org/User:Mvidner
Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
Duncan Mac-Vicar Prett napsal(a):
Patches now have bugzilla and security metadata. I already added support
for displaying them in the user interface. However I am thinking on zypper
now.
An user may want to say zypper "install the fix for bugzlla 3223".
We have 2 ways to implement this, and I would like to hear your feedback:
- use the current metadata to search for the issue and mark packages for
install. This will need some "look" code in each application.
Add to libzypp method which can install/uninstall query. something like in
locks (addLock(query)) so install(query). frontend only fill query and send
that want install result of it. So "look" code can be really short.
"Uninstall all packages with careless maintainers" ;-)
zypper rm `zypper se --search-descriptions teh`
zypper in -t patch `zypper se -d -t patch BNC#38810`
Well OK, we would need to remove the formatting from the search
output...
Pepa
- Use the solver, and during parsing inject something like
provides:fix(bugzilla:23444) when filling the repodata. Then applications
could inject a requires in the solver fix(bugzilla:23444) and just solve.
I dont't know the consequences of this.
It is cleaner than having to search the free form description.
Now that I think of it, having the patch metadata in a form
different from Provides seems wrong, because that only forces you to
write new code for what is served by Provides better.
--
Martin Vidner, YaST developer
http://en.opensuse.org/User:Mvidner
Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |