On Tue, Jun 08, 2004 at 11:30:58PM -0400, Michael P. Soulier wrote:
> On 08/06/04 Joe Orton said:
>
> > Well, think about it: it would require doing things like a "find /" to
> > find all the repositories, and stopping any svnserves or httpds which
> > are using them before doing a dump/load on each, then starting the
> > daemons again. All from a %post script: not clever, indeed.
>
> A typical Debianism once painted into a corner like this would be to
> supply a tool to migrate the repositories, and merely notify the users
> of them during the upgrade via a post script. I've been bitten by such
> things occasionally when they were very unexpected, but typically they
> are a great help.
Supplying the tool is easy enough, but there's no way of notifying the
user of the correct process for using it during the package upgrade.
%post scripts are not interactive nor are they supposed to produce
output (stdout is not useful if you're using a GUI package update tool,
for instance).
And I say again: it is *never* expected that a package update breaks
anything which was supposed to be working before. There needs to be a
very good reason to break that rule, and "oh, but this new version is
*so* much better" is not good enough IMO.
Anyway, I think we're in danger of getting off-topic now (or at least
off-Subject). :)
joe
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 9 10:47:40 2004