Hi, Le 10/03/2014 10:50, Оlе Ѕtrеісhеr a écrit : > [packaging ESO MIDAS] > Let's see how far I come. BTW, Since I do not use it myself: Is it worth > to split it into core, applic, stdred, and contrib packages? Is there > any use for keeping the source?
It's already great to package it, don't overdo it. You won't have that many installs anyway, and most users will want the full package. I don't see a need for keeping the source either. I would split like this, depending on whether it makes sense: - midas (binary arch) - midas-common (binary indep, if it is big) - midas-doc (if it is big, else with -common) If MIDAS supports plug-ins (that, I don't know), then you could put the files that are needed only for compiling extensions in midas-dev. > I was looking for an automated way. I would just do the following: > > * put all files that are obviously system dependent to /usr/lib > * put all files that are obviously system independent to /usr/share > * Check all other files and put them to the right place That works, too. > However, this is (as well as your proposal) manual work, and has to be > repeated with each release. Therefore I was hoping to have the majority > of files automatically put to the right place and deal only with the > ones where the automatic way fails. I doubt the list of files for this mature piece of software will change much between releases. Kind regards, Thibaut. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/531d8f34.7080...@free.fr
