On Sat, Jan 15, 2011 at 12:37 AM, Ahmad Samir <[email protected]> wrote: > On 15 January 2011 01:18, Maarten Vanraes <[email protected]> wrote: >> Op vrijdag 14 januari 2011 13:22:54 schreef Colin Guthrie: >>> Hi, >>> >>> When importing packages, I'm very tempted to not import esound. It's >>> only used to compile libesd. Do we really need it? >>> >>> I don't think we ship any apps that use only esd, so I don't think >>> that's a problem but perhaps some old legacy apps (i.e. games) still >>> need it. >>> >>> What do people think? It's not really much hassle to support it, but by >>> the same token, dead projects have to be buried at some point! >>> >>> Col >> >> I don't fully agree, dead projects can stay alive (undead). >> >> however, just don't import it, don't have support for it in gnome. and if >> someone really needs it, he can import it and maintain it if he wants to. >> >> in short, drop it and let someone else figure it out at a later date. >> > > Well, no, dead projects are just that, dead... > > And if libesd is dropped all packages that BR it need to be fixed; > maybe postpone this until the importing rush is over, then it can be > phased out after this high pressure stage is over.. (just MHO). > > -- > Ahmad Samir >
i think coling is right and this is the best moment to drop packages as we won't have to rebuild anything after dropping it
