Daniel Knabl <[EMAIL PROTECTED]> wrote: > The main target in postinst, when someone initially installs the > software, is "configure",
No, not only upon initially installing it. On every upgrade. > and in postrm, when someone purges it, it is > "purge". No, if the package is purged, postrm is called twice, with different arguments. And it's also called when the package is upgraded or removed. > Now it seems, that I should also perform actions on some targets that As I understood Marc, you did some actions unconditionally, no matter what the first argument is (that seems to be fixed now), and some in configure unconditionally on the second argument that should not be performed upon upgrade. This you still do. Err, and you keep configuration files in /usr/share. > do not get used in real installation process: who should upgrade the > package, when there has never been a version of it before? The package could be in state rc. > Who should downgrade the package (to a non-existent version before)? I > did some tests (installing, removing,purging ...) and there was no > unexpected behavior. > > So now I don't understand, really NOT understand, what you are > complaining about? Is it because I want to release a piece of software > that you don't like? It's a software whose quality I cannot judge, but the quality of the packaging is not fit for Debian. > Is it because of me as person? > If there's any other place where I could ask, not just "if there has > something to be done", but "what in special case has to be done", then > please pint me over there. No problem for me to getting told that this > is the wrong list too, but anyone should even tell me then ... It's the right list for asking questions after you've tried to understand the Debian policy, and consulted the Developer's reference where Policy is unclear to you. But it seems you haven't read the policy, or > I followed your suggestions not to ask on debian-devel, and i have read > the policy more often now, especially the chapters 6.5 to 6.7 about > control files and their behavior, but there are still questions that > affect the actual state of the package. you didn't understand it. Sections 6.5 to 6.7 deal with the installation procedure and maintainer scripts. Control files only exist in the source package. And what you wrote above about postinst and postrm can also easily be shown to be false (or at least incomplete) by looking at these sections. Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX)
