Stefano Zacchiroli wrote: > PS regarding the other part of this thread about how to support, via > backports, what I would call "rapidly evolving end-user apps", it is > surely a worthwhile discussion, more general than Chromium. I believe > it would be worth to have it elsewhere (e.g. -devel), possibly once > the needed feature requests (e.g. on APT) have been implemented. Note > that unless there is a chance to get those features into Squeeze, > it's probably a too-late-coming discussion.
I'm jumping in. I was quite surprised to see that the proposed solution was to put Chromium in backports rather than in volatile. I don't really mind, as long as it's supported somehow, but then, what's the point of volatile? Also, I have found that Pidgin would really have been a valid candidate for volatile: after few months, Yahoo, MSN and other networks are changing, and it becomes simply impossible to log into these networks unless you upgrade Pidgin (or some of its protocol purple libs) to a higher upstream version. Wouldn't it make sense to have Desktop apps like these (I suppose there are other examples, like maybe the flashplugin-installer package in non-free) sit in volatile? Just my 2 cents idea, Thomas DISCLAIMER: I'm not willing to work on Desktop applications, this isn't my field, I have enough work on server packages. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c891a7d.5010...@debian.org
