Guy Maor writes ("Re: Purging database packages"):
> "Oliver Elphick" writes:
> > I interpreted the sentence `No attempt is made to unwind after errors during
> > removal.' to mean that exit status is not checked. Is that the case?
>
> ? I would
> >I thought it only implied one bit of configuration information somewhere
> >under /etc/.
Oliver Elphick wrote:
> Yes, but this is a particular case of the general problem of interactive
> installation scripts. Furthermore, this particular case is one that is a
> bit extreme: on installin
Raul Miller wrote:
>> >I would like to see a way to preemptively indicate that the
>> >data should not be deleted. In a busy environment with several
>> >sysadmins, you want to be able to make such decisions ahead of
>> >time.
>
>Oliver Elphick wrote:
>> This seems a good ide
Oliver Elphick wrote:
> >> 3. Should there be policy on this matter for database packages in
> >> particular?
Raul Miller wrote:
> >I would like to see a way to preemptively indicate that the
> >data should not be deleted. In a busy environment with several
> >sysadmins, you want to be abl
Raul Miller wrote:
>Oliver Elphick wrote:
>> 3. Should there be policy on this matter for database packages in particul
>ar?
>
>I would like to see a way to preemptively indicate that the data
>should not be deleted. In a busy environment with several sysadmins,
>you want to be
"Raul Miller" <[EMAIL PROTECTED]> wrote:
> > I would like to see a way to preemptively indicate that the data
> > should not be deleted. In a busy environment with several sysadmins,
> > you want to be able to make such decisions ahead of time.
Jules Bean <[EMAIL PROTECTED]> wrote:
> Can't you us
--On Mon, May 18, 1998 12:46 pm -0400 "Raul Miller" <[EMAIL PROTECTED]>
wrote:
> Oliver Elphick wrote:
>> 3. Should there be policy on this matter for database packages in
particular?
>
> I would like to see a way to preemptively indicate that the data
> should not be deleted. In a busy enviro
Oliver Elphick wrote:
> 3. Should there be policy on this matter for database packages in particular?
I would like to see a way to preemptively indicate that the data
should not be deleted. In a busy environment with several sysadmins,
you want to be able to make such decisions ahead of time.
-
Guy Maor <[EMAIL PROTECTED]> writes:
> "Oliver Elphick" writes:
>
> > case answer in
> > y|Y|YES|yes|Yes)
> > rm -rf postgres/data
> > ;;
>
> Should you not add
> *) echo "Purge aborted."; exit 1;;
>
> ?
But that defeats
"Oliver Elphick" writes:
> I interpreted the sentence `No attempt is made to unwind after errors during
> removal.' to mean that exit status is not checked. Is that the case?
? I wouldn't have thought that was the case, but now am not sure.
Guy
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
> When a database package is purged, the implication is that the data
> stored in the database should also be deleted. Therefore I have
> added the instructions to delete the data to postgresql's postrm.
>
> However, since it is possible to flag whole groups of packages for
> purging when using d
Guy Maor wrote:
>"Oliver Elphick" writes:
>
This is in the context of `postrm purge':
>>case answer in
>>y|Y|YES|yes|Yes)
>>rm -rf postgres/data
>>;;
>
>Should you not add
>*) echo "Purge aborted."; exit 1;;
"Oliver Elphick" writes:
> case answer in
> y|Y|YES|yes|Yes)
> rm -rf postgres/data
> ;;
Should you not add
*) echo "Purge aborted."; exit 1;;
?
Guy
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject o
On Mon, May 11, 1998 at 02:30:26PM +0200, Oliver Elphick wrote:
> When a database package is purged, the implication is that the data stored
> in the database should also be deleted. Therefore I have added the
> instructions to delete the data to postgresql's postrm.
>
> However, since it is pos
Oliver Elphick writes:
> Now, section 2.3.8 of the Policy Manual states that we should minimise
> interactive prompting while installing; it does not even contemplate the
> idea of prompting in the removal scripts.
That section of the Policy Manual says, "Packages should try to
minimise the
"Oliver Elphick" writes:
> When a database package is purged, the implication is that the data stored
> in the database should also be deleted. Therefore I have added the
> instructions to delete the data to postgresql's postrm.
>
> However, since it is possible to flag whole groups of packages
I'm raising this issue in relation to PostgreSQL, but I am also copying to
the maintainers of msql and mysql, for whom the same issues must be relevant.
When a database package is purged, the implication is that the data stored
in the database should also be deleted. Therefore I have added the
i
17 matches
Mail list logo
