[pacman-dev] String freeze for 3.2 release
ngaba at bibl.u-szeged.hu
Wed Jul 16 14:18:21 EDT 2008
> only happen on error cases, and they are relatively small.
> The question is how. Dan does not want to make these free functions
Why? I can't see too much difference between alpm_miss_get_causingpkg
(wow, new API change ;-) and alpm_miss_free.
> ... Maybe we want to store these error lists in libalpm, and
> allow the frontend to get it. And then it would be freed when the
> transaction is freed?
I don't like this. We should somehow differentiate pmdepmissing_t and
pmconflict_t ... lists, and we have more chance to do memleaks here.
> Otherwise, maybe this is where it would help to have a free function
> attached to the list structure.
> > 4. <flame> Revert vercmp code to 3.1 </flame>
> It would be nice to figure out what changed and why it doesn't work
> anymore rather than simply reverting.
nicer, but harder ;-)
See 84283672853350a84d2a71b72dc06e180cad1587, search for 'type
More information about the pacman-dev