Re: RFS: anagramarama - fast paced anagram puzzle game using SDL
On Tue, 2005-01-18 at 14:27 +0100, Bartosz Fenski aka fEnIo wrote: > On Tue, Jan 18, 2005 at 07:53:06AM -0500, Ryan Stutsman wrote: > > Any takers? It's a very simple package. > > Didn't you think about splitting it to two packages? > Consider that Debian supports 11 archs right now. I have considered it; however, the reason for the size is because of a couple of BMP files I'm hoping to have them convert to PNG files upstream which should cut down significantly. After looking at it more I found not all of the images in the source directory are used in the code so I removed them from the make install which knocks the file down to under 200 KB. Once I am sure of what the intentions are for the next release upstream I will decide whether to split the package or not. It's possible I could get the package to be even smaller working with the authors a bit. > Your package is 800k big. > > 11 * 800k = 8,8M > > Using one binary dependent package + one independent that would be: > > 11 * 30k + 770k = ~ 1MB > > I know it's not very much, but Debian's archives are very big and overloaded, > and we should search for savings everywhere ;) > > Also remove your README.Debian file, cause it is not saying anything > interested and related to Debian. This is done. > > regards > fEnIo Thanks for taking the time to look at it and for the suggestions. Please take another look if time allows! Ryan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: (2nd try) bmon - Command-line bandwidth monitor and rate estimator
Hi Sven On Tue, Jan 18, 2005 at 06:01:03PM +0100, Sven Mueller wrote: > >According to the developer static linking isn't possible. Anyway, the > >feature isn't that important, I hope I can integrate it in a later > >version. > > I would file an RFP: libnl at least. Maybe someone else picks it up and > creates the libnl package for you. Then it would simply be a matter of > Build-Depends/Depends to add the libnl dependent features. Good idea, I'll do that. Thanks! Reto Schüttel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: (2nd try) bmon - Command-line bandwidth monitor and rate estimator
On Sun, Jan 16, 2005 at 09:38:43PM +0100, Reto Schuettel wrote: > I'm still looking for a sponsor for bmon. Finally I found somebody :). Christoph Haas has sponsored the package (thanks!). Thanks for the help! Reto Schüttel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: (2nd try) bmon - Command-line bandwidth monitor and rate estimator
Reto Schuettel wrote on 17/01/2005 12:48: Hi Simon On Mon, Jan 17, 2005 at 12:22:04PM +0100, Simon Richter wrote: You could package a static build of libnl and omit the shared library, which is usually the way to go with unstable ABIs. According to the developer static linking isn't possible. Anyway, the feature isn't that important, I hope I can integrate it in a later version. I would file an RFP: libnl at least. Maybe someone else picks it up and creates the libnl package for you. Then it would simply be a matter of Build-Depends/Depends to add the libnl dependent features. cu, sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: anagramarama - fast paced anagram puzzle game using SDL
On Tue, Jan 18, 2005 at 07:53:06AM -0500, Ryan Stutsman wrote: > Any takers? It's a very simple package. Didn't you think about splitting it to two packages? Consider that Debian supports 11 archs right now. Your package is 800k big. 11 * 800k = 8,8M Using one binary dependent package + one independent that would be: 11 * 30k + 770k = ~ 1MB I know it's not very much, but Debian's archives are very big and overloaded, and we should search for savings everywhere ;) Also remove your README.Debian file, cause it is not saying anything interested and related to Debian. regards fEnIo -- _ Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | IRC:fEnIo _|_|_ 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Polska (0 0)phone:+48602383548 | proud Debian maintainer and user ooO--(_)--Ooo http://skawina.eu.org | JID:[EMAIL PROTECTED] | RLU:172001 signature.asc Description: Digital signature
Re: RFS: anagramarama - fast paced anagram puzzle game using SDL
Any takers? It's a very simple package. On Sat, 2005-01-15 at 22:10 -0500, Ryan Stutsman wrote: > Hello, > > I've been through a few iterations with this package on this list > implementing suggestions. > > Please have a look at the latest incarnation if you could, and give me > any feedback. > > Hopefully I'm getting closer ;) > > Binary and source pkgs available at > > http://www.cs.purdue.edu/homes/rstutsma/debian/ > > Thanks much, > > Ryan > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: best way to announce important changes
Christoph Wegscheider <[EMAIL PROTECTED]> wrote: > Hi, > I maintain the rsnapshot package, which is a perl script for backups. > > In the next upstream version there will be changes which WILL break > almost all setups. One has to modify the conf file to avoid that. Is it a conffile or just a configuration file? > According to the developer reference (6.3.4) such changes should be > mentioned in the News.Debian file. I think that's not enough, because > if one doesn't change the conf file rsnapshot will not fail, but will > do things (most likely) not wanted by the user. Therefor I intend do > show a warning with debconf. Depending on the severity of "not wanted", you could simply disable the script until the configuration file has been fixed. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Re: best way to announce important changes
On Tue, Jan 18, 2005 at 10:00:08AM +0100, Christoph Wegscheider wrote: > I maintain the rsnapshot package, which is a perl script for backups. > In the next upstream version there will be changes which WILL break > almost all setups. One has to modify the conf file to avoid that. > According to the developer reference (6.3.4) such changes should be > mentioned in the News.Debian file. I think that's not enough, because > if one doesn't change the conf file rsnapshot will not fail, but will > do things (most likely) not wanted by the user. Therefor I intend do > show a warning with debconf. > Are there better solutions? Fix your package so that on upgrade, it properly updates the config file so that it *doesn't* do things not wanted by the user! Neither debconf notes nor NEWS.Debian are an excuse to break a user's system. If you're breaking a config interface and it is possible to migrate old settings to the new (i.e., you don't have to worry about user config files scattered through various home directories), there is no reason not to do so. Rather, these are the enhancements that explain *why* people choose Debian. If for some reason this isn't possible, then and only then should you use NEWS.Debian to document the issue. But not a debconf note -- debconf notes are not and never were intended for this. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: best way to announce important changes
On Tue, Jan 18, 2005 at 10:00:08AM +0100, Christoph Wegscheider wrote: > According to the developer reference (6.3.4) such changes should be > mentioned in the News.Debian file. I think that's not enough, because > if one doesn't change the conf file rsnapshot will not fail, but will > do things (most likely) not wanted by the user. Therefor I intend do > show a warning with debconf. Don't bother with the Debconf stuff. Put it in NEWS.Debian and README.Debian. If the config file has really changed in that way, then move it out of the way, and ensure that the program will bomb (possibly with an appropriate error message) in the absence of the config file. - Matt signature.asc Description: Digital signature
best way to announce important changes
Hi, I maintain the rsnapshot package, which is a perl script for backups. In the next upstream version there will be changes which WILL break almost all setups. One has to modify the conf file to avoid that. According to the developer reference (6.3.4) such changes should be mentioned in the News.Debian file. I think that's not enough, because if one doesn't change the conf file rsnapshot will not fail, but will do things (most likely) not wanted by the user. Therefor I intend do show a warning with debconf. Are there better solutions? Thx Christoph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
