Bug#747256: Chocolate Doom should be split into separate packages
Package: chocolate-doom Version: 2.1.0-1 Followup-For: Bug #747256 I think this is more severe than just wishlist, since it installs menu items for things which DO NOT WORK when you click on them (e.g. Chocolate-Heretic is in the games menu, but absolutely nothing happens when you select it, not even an error message about missing game data). -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages chocolate-doom depends on: ii doom-wad-shareware [doom-wad] 1.9.fixed-2 ii libc6 2.19-13 ii libpng12-0 1.2.50-2+b2 ii libsamplerate0 0.1.8-8 ii libsdl-mixer1.21.2.12-11+b1 ii libsdl-net1.2 1.2.8-4 ii libsdl1.2debian1.2.15-10+b1 ii zlib1g 1:1.2.8.dfsg-2+b1 chocolate-doom recommends no packages. Versions of packages chocolate-doom suggests: ii zenity 3.14.0-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747256: Chocolate Doom should be split into separate packages
Late reply so apologies for not responding sooner. On 8 May 2014 03:16, Fabian Greffrath fab...@greffrath.com wrote: With the split approach I would also have to separate -server and -setup into different packages and introduce rather complex inter-package dependencies. Chocolate Doom's 'make install' rule installs separate copies of chocolate-setup as chocolate-doom-setup, chocolate-heretic-setup, etc. There isn't actually need to make a common package and use symlinks. As for chocolate-server, I've actually stopped distributing binaries of this for other platforms because I think it's misleading. People get the mistaken impression that they need to run a dedicated server if they want to play a network game and most of the time this isn't the case. Usually one of the clients acts as a server; if necessary it's possible to run a dedicated server as chocolate-doom -dedicated. The only situation in which you'd want to use chocolate-server is if you were running it as a permanent dedicated server (the one that appear on master.chocolate-doom.org). Very few people do that. If you want Debian to support that use case it should probably be a separate package anyway, as chocolate-server is a smaller binary that doesn't have all the dependencies of the main client binaries. -- Simon Howard https://soulsphere.org/
Bug#747256: Chocolate Doom should be split into separate packages
I don't agree that split packages is really about file or download sizes. The way I see it, a split package would fairly represent desires to install the games separately as their own entities. For example, if someone only cared about Hexen, they should be capable of installing _only_ a chocolate-hexen package, ignoring Doom, Heretic, and Strife. This also would free up the desktop menus (or app drawer, however any particular desktop implements them) from icons for games that they may never play nor care about. If file size were really the concern, I could probably place an argument about *any* package ever being split in the age of terabyte hard disks and people generally having hundreds of gigabytes free -- even LibreOffice is only ~400MB, why bother installing only Writer to save a few MB from that? I just personally don't see split packages as being a concern about file or download size. It might be a nice side-benefit, sometimes, but it's not really about that. For what it's worth, I maintain the Chocolate Doom package in Arch Linux's AUR, and since 2.0.0 came out, I have kept it as split packages, pretty much for the sole reason of allowing people to keep only the games they care about. To solve the issue with setup and server binaries, I made a chocolate-common package that the other four packages depend on. You can see the PKGBUILD here: https://github.com/chungy/aur/blob/master/chocolate-doom/PKGBUILD -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747256: Chocolate Doom should be split into separate packages
Hi fraggle, Am Dienstag, den 06.05.2014, 15:39 -0400 schrieb Simon Howard: Version 2 of Chocolate Doom added support for Heretic, Hexen and Strife. The compiled binaries and manpages for the four games are effectively separate, but Debian is currently distributing them as a single package. It would make more sense to split them into four separate packages so that people can just install the game(s) they want to play. hm, as briefly discussed before, I am still not sure what this is supposed to achive. The whole package is about 3MB - unpacked. With the split approach I would also have to separate -server and -setup into different packages and introduce rather complex inter-package dependencies. Also, what should happen on upgrade? Not sure about that. :/ Cheers, Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747256: Chocolate Doom should be split into separate packages
Package: chocolate-doom Version: 2.0.0-2 Severity: wishlist Version 2 of Chocolate Doom added support for Heretic, Hexen and Strife. The compiled binaries and manpages for the four games are effectively separate, but Debian is currently distributing them as a single package. It would make more sense to split them into four separate packages so that people can just install the game(s) they want to play. -- Simon Howard https://soulsphere.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
