Re: What to do about the situation with id3v2
On Thu, Apr 28, 2011 at 11:29, Adam Borowski <firstname.lastname@example.org> wrote:
>> In case you are thinking of dropping libid3, the following are the
>> reverse deps and reverse build-deps that would need to be ported or
>> dropped. You might want to talk to their maintainers and upstreams:
> [15 packages]
> But this is an argument to keep it. Porting 15 packages to something else
> would be quite a bit of work.
> However, what if you made not the command line tool but the library a thin
> wrapper over a competing one? That would require porting just once.
Someone also suggested this on IRC last night and I actually like the
"You are not Grey Squirrel?"