FS#7428 - [ALPM] remove IgnorePkg entries

Attached to Project: Pacman
Opened by Georg Grabler (STiAT) - Tuesday, 12 June 2007, 08:03 GMT
Last edited by Dan McGee (toofishes) - Monday, 31 December 2007, 05:11 GMT
Task Type Feature Request
Category Backend/Core
Status Closed
Assigned To Aaron Griffin (phrakture)
Dan McGee (toofishes)
Architecture All
Severity Medium
Priority Normal
Reported Version 3.0.4
Due in Version 3.1.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I'd like to see the opposite to alpm_option_add_ignorepkg(const char* pkg), so alpm_option_rem_ignorepkg(const char* pkg).

Simply for the reason that i can force installations then (in example if a depend is exactly to a version for a program a user requested, i can ask and force the installation afterwards).

Also, it might be interesting for several other options.

Yours,
Georg
This task depends upon

Closed by  Dan McGee (toofishes)
Monday, 31 December 2007, 05:11 GMT
Reason for closing:  Implemented
Additional comments about closing:  Implemented in GIT
Comment by Georg Grabler (STiAT) - Wednesday, 11 July 2007, 16:27 GMT
Probably a total bullshit i wrote.
Of course, it just brings a cleaner interface, if i cannot just add but also remove ignorepkgs, favoring "running" programs, where the lib is loaded (and initialized) alredy.

For now, pyalpm handles this completely itself, but i'd rather like a direct mapped interface to alpm...

Also, for addIgnoreDB / remIgnoreDB, addHoldPkg / remHoldPkg and all those "configuration" interfaces.
Comment by Aaron Griffin (phrakture) - Wednesday, 11 July 2007, 16:41 GMT
I think all these list functions make a lot of sense. All of the list config settings that have 'add' functions by _content_ probably also need a remove by _content_

I'm going to add Dan on here, in case he gets in the mood to do something quick like this - I'm still catching up on a lot of pacman stuff I've missed.
Comment by Georg Grabler (STiAT) - Tuesday, 17 July 2007, 10:39 GMT
Indeed, it's very useful for API interfaces, since it makes them very easy to use (of my point of view).

I'll take the step to talk dan next week, when i'm finally back from holidays. Got a sunburn already anyway ;).

I've some plans on especially the config and list options to be modified. For a proper design, i'm currently stepping trough the current git branch, and try to figure out where else it would be useful.

Loading...