Manoj Srivastava wrote: > >> But some of people-written snippets have, often doing it wrong. > > Can you point to some examples? Have you filed bug reports? I filed #552389, a good example (IMO) of confusing due to complexity. There are plenty of packages that do checks of parameters that are passed to script and then doing completely nothing with them. Some packages tend to think that 'disappear' is equal to 'remove', others think that it's equal to 'purge', so either first or second set is doing wrong.
>>> I also think that there might be packages that take specific >>> action on those cases in the future; since in all cases packages are >>> being removed or disappearing. Having information that distinguishes >>> which part of the state transition is in effect is information may >>> be useful, and I see little benefit in removing it. > >> Can you elaborate on this? Not for convincing me, I'm just curious how >> the package can take different actions on removal depending on what >> package is the case of removal. > > What do you mean, how? Are you asking me a basic scripting > question? If not, I am failing to understand what you are asking. Of course, not. I questioned how this info can be useful, not how to write a code for it. > In any case, look at /var/lib/dpkg/info/ucf.postinst > > It gives examples of where things can be put in, were you > inclined to do different things based on how the script is called. It gives only a code template to do different things, but actually does nothing. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer
signature.asc
Description: OpenPGP digital signature
