OK, seems i've found some kind of solution: https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintscriptpropmpt The config script might be run before the preinst script and before the package is unpacked or any of its dependencies or pre-dependencies are satisfied. ___Therefore it must work using only the tools present in *essential* packages___
So the only way it to mark libxyz-common-tools as Essential? But i think it is a little bit overkill because for me libxyz-common-tools isn't really essential by mean of system-wide. May be there's another solution? 2014-12-29 0:58 GMT+02:00 Russ Allbery <r...@debian.org>: > "Yuri Oleynikov (יורי אולייניקוב" <yur...@gmail.com> writes: > > > But, when installing packageA without libxyz-common-tools is > > preinstalled - packageA.config script won' run? > > > Is there any way to solve the problem? > > The config script runs during a preinstall stage, before the package > dependencies are installed. I think that you can work around this by > having your internal packages use Pre-Depends for the package that > provides your script library (instead of Depends). > > -- > Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> > > > -- > 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/87a927fkke....@hope.eyrie.org > >
