Well that's the thing.. I don't want to package tktray with aMSN.. I don't think that it's a wise choice. I think it's better to leave things outside of aMSN as much as possible.. let the ubuntu/debian/fedora/whatever packagers take care of adding the 'Depends: tktray' line, that's it... why should we do that? If we include tktray, we'd start fixing it and have our own code in there, and we'll start maintaining it, etc.. and I don't want that.. if there's an issue, we should report it to the original author.. if he doesn't have time or whatever to fix it, then we could fix it and send the patch and ask people to upgrade their tktray version.. as simple as that. However, I would agree that we might need to set up our own PPA that would have tktray pre-built for the users.
On Wed, May 12, 2010 at 8:03 PM, Alexander Nestorov <alexander...@gmail.com>wrote: > Congrats on that patch kkrt! > > Maybe we should package amsn with tktray? It's only +100kb (if size > matters) and we'll avoid > making users install tktray. > Maybe we should check if tktray is installed on the system, if "yes" and if > installed version is newer > that the version we packaged with amsn, use it, else use own tktray. > (We really should get rid of current tray code) > > > -- > alexandernst > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > Amsn-devel mailing list > Amsn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amsn-devel > >
------------------------------------------------------------------------------
_______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
