> What can we do to avoid this? > > I don't have any definite answers although there are ideas to > explore: > > - we could relax our requirements and have a way to document the > limitations of those packages (wrt our usual policies) > > - we could ship those applications not as .deb but as container > and let them have their own lifecycle > > What do you think? Do you have other ideas? Are there other persons > who are annoyed by the current situation?
Can't we treat a .deb file like a container in the sense that it may include additional source if needed? I'd very much like this. I know that this does create some problems for us, e.g. on the security side, but the alternative is, as you mentioned, manually installed software and that surely is worse. Maybe we should restrict this approach to areas where this problem is very common, like javascript? At least initially. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Meskes at (Debian|Postgresql) dot Org Jabber: michael at xmpp dot meskes dot org VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL
