On Sat, Mar 7, 2009 at 12:10 AM, Sandro Tosi <mo...@debian.org> wrote: > On Fri, Mar 6, 2009 at 23:44, Mikael Djurfeldt <m...@debian.org> wrote: >> Package: wnpp >> Severity: wishlist >> Owner: Mikael Djurfeldt <m...@debian.org> >> >> * Package name : music >> Version : 1.0.1 >> Upstream Author : Name <mik...@djurfeldt.com> >> * URL : http://software.incf.org/software/music/home >> * License : GPL >> Programming Lang: C++ >> Description : ITP: music -- Multi-Simulation Coordinator for MPI > > I think "music" is a too generic name, even more that his package has > nothing to do with music (in the sense of sounds with a certain > harmony and timings).
Well, you'd be surprised how much this software has to do with timing! It orchestrates the data flows in clusters and directs the participating applications according to a timing schedule so that they work in harmony. :-) More seriously, we have one problem here: The name of the upstream software could probably be regarded as written in stone by now since the project has been running for two years and the research organization initiating it (INCF) has invested a lot in the name within the field. So, the question then becomes how to deal with it in the best way for Debian. The main component of MUSIC is a library---you link with it along with mpi (-lmusic). I think it could cause confusion if the library had a different name when working as a developer under Debian. > I dunno the field that much, but maybe "mpi-music" or so can be better. What about renaming the source package to incf-music but keeping the names of the packages generated from it (libmusic1, libmusic-dev etc)? > Thanks for considering, Thanks for your input! Best regards, Mikael D. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
