Public SourceMage Discussion List

[Hamish Greig <hgreig AT bigpond.net.au>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 21 Nov 2003 01:03, Robin Sheat wrote:
> Just curious, is the condition of qt-x11 conflicting with itself always
> going to be there?
> It is somewhat annoying, as it means Qt apps can't be started while Qt
> is taking its decade to compile.
> However, if it is only there on major upgrades, then I'm happy to grin
> and bear it. (Hmm, I wonder if there is any possbility of making it
> remove the conflict when it has successfully installed? Just a thought)
It is definitely needed for major upgrades and given our "discussed" policy 
of 
maintaining "fixes" for a period of some months (a few releases) it will 
probably need to stay there permanently.
A lot of other spells also need special consideration for major upgrades, it 
would be worth implementing a sorcery feature to "detect" how serious an 
upgrade is and whether is should conflict with the installed version. Many 
other spells that have triggers would benefit from this also, as many 
triggers only need casting once for a major update, for minor updates or 
sorcery rebuild they don't need to be triggered.
Robin, when you have finished studying sorcery code and implemented this, 
I'll 
by you a beer.
Hamish
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/vM9D8fSufZR6424RAlVKAJ9M5zGalZX8awOLzU4UA6FLkV0MMACfYd5A
W4wGTKbEzjXNdlPpaeXJqrg=
=hZK4
-----END PGP SIGNATURE-----