Hello, The Chicken community is indeed small in size, but I still don't see this as a reason why Debian should make it more difficult to access the Chicken compiler -- on the contrary, Debian should be a vehicle for the wider dissemination of free software. One of the reasons to choose Debian listed on its web site is that it "comes with over 18733 different pieces of software". I don't think this means 18733 weirdly-configured pieces of software.
I am happy with your proposal to add a post-install script to chicken-bin that makes a symbolic link to csc if /usr/bin/csc does not exist, but what happens if the user installs mono after chicken-bin? If the mono-devel package can recognize that there is a csc symlink and remove it, this would be an adequate solution for me. -Ivan Mirco Bauer <mee...@debian.org> writes: > AFAIK the alternatives system is not to solve conflicts of application > names in /usr/(s)bin but to provide an uniform invocation of different > implementations with the same goal (e.g.: terminal, browser, c-compiler, > java-compiler, csharp-compiler). In this case the Chicken compiler and > the C# compiler don't share any functionality though (besides that they > compile something). > > Also for build-deps, this would not insure by default that the correct > command would be used (as chicken and mono-devel could be installed) > leading to unwanted build-conflicts on both sides (package that use > chicken in build-deps and packages that use mono in build-deps). > > So unfortunately I don't see any decent solution in this matter. Even > if mono-devel would have a binary conflict against chicken, that would > mean they have to be moved from optional priority to extra and with > that the whole chain of packages that use it (~100 source packages > on the mono side). > > Without wanting to put chicken down, popcon of chicken shows 85 > installs while mono-gmcs (the current C# compiler) shows 2115 installs. > > I wonder if it's policy conform that chicken-bin installs a csc symlink > to csc.chicken at postinst stage if there is no csc present (no > mono-devel installed). That would be a solution between conflict and > alternatives, ensuring chicken users are happy without interfering with > the mono build system and all source packages relying on it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
