Hi, On 01.06.2013 16:10, Christian Welzel wrote: > If i'm not using depends, its not garanteed, that apache2 is configured > before my package, right? If the new package (mine) gets configured > before apache2 (alphabetical order or whatever reasons) the above check > would return false and the apache2.2 code would wrongly be skiped, > wouldnt it?
True. But it makes no difference, as unpacked is good enough to you. All you want to know is "is Apache 2.2 (going to be) installed" or not. I guess, if you change it to elif [ "$COMMON_STATE" = "installed" ] || [ "$COMMON_STATE" = "unpackaged" ] ; then ... it is good enough. Having that said, I don't think there is a situation where you get Apache in the same dpkg/apt run because it's recommended, but without being configured before. I don't think either, that's guaranteed though. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D
signature.asc
Description: OpenPGP digital signature
