Package Installation behavior

[Onno Benschop]

On 12/08/07 08:32, Bruno Clermont wrote:
> Hi guys,
>
> I searched on google, asked on IRC & forums... you are basically my
> last chance:
>
> I'm building debian packages that run on Ubuntu and I need to test
> them. One great thing for that is debootstrap and then I install my
> packages into the freshly created virgin Ubuntu system.
>
> But one thing that bother me is that by default, when apt-get install
> a package that provide a service running constantly, such as apache2,
> the process is started RIGHT AFTER the package is installed.
>
> Is there a way to prevent a service to start (or restart) when a
> package is installed (or upgraded). Like debootstrap is doing.
>
> The main goal is to be able to debootstrap Ubuntu, then chroot into it
> and install package and be sure it won't mess the host.
>
> And I'm looking for a solution that apply to dapper and newer release.
>
> thanks! 
The way I've seen packages do this is by checking for the
(non-)existence of a file before starting the service. That way the
service won't start until it's configured.

-- 
Onno Benschop

Connected via Optus B3 at S31°54'06" - E115°50'39" (Yokine, WA)
--
()/)/)()        ..ASCII for Onno..
|>>?            ..EBCDIC for Onno..
--- -. -. ---   ..Morse for Onno..

ITmaze   -   ABN: 56 178 057 063   -  ph: 04 1219 8888   -   onno at itmaze.com.au