-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Ivan,
On Thursday 08 November 2001 18:08, Ivan E. Moore II wrote: > > > > I don't see why out of this box this wouldn't work. This should work > > since that is how a kde hacker does a local kde compilation for CVS HEAD > > beside his stable KDE installation. > > > > It *would* work, but you can't use either /opt or /usr/local as KDE > > installation dir because it would break fhs. > > and how will the end user swap back and forth? And how would a user have > a mixed installation? > > You haven't thought this out and I am now done trying to explain this to > you. > I have of course thought it out, I simply did not elaborate enough of that in that mail. The end user will normally _not_ swap back and forth. It's error prone.[*] My aim is to provide for existence of a kde-cvs-dev package that will enable installation of all (recent) development related packages while co-existing with a stable KDE installation as I have said. What I'm saying is strictly for developers who would like to develop for KDE. There are a good number of KDE hackers who are not following these mailing lists (and using Debian) I'm certain that they would find such support invaluable. However, I'd like to stress once again that my concern is development packages and not application packages. I believe that this environment exists not only for users but developers and the current set of packages will not be usable for developers because most developers will not want to leave the nice stable environment only to be able to write a tiny application. And as I have said using the CVS (or recent) versions while using a stable installation is the recommended procedure for hacking KDE. I hope I've made my point clear. In the current state very few people will make use of kde*cvs*dev packages. They'll have to compile from CVS themselves. But if we gave them some alpha release more people would be tempted to write an app or plugin for KDE3 which will be beneficial for free software in general. I kindly request you to give more thought to this issue. If any help is needed please tell me what is needed, what I can work on and I'll most certainly try to be of assistance. As I said any range of fixing is within my ability, and I'd certainly like to see this happen. If you'd like we can work on the alpha branch right now, and see what we can do. If it works that can be carried to HEAD. Thanks for your interest, [*] Here's what we can do for users: Applications will (or may) conflict. It's plausible as you have explained. I agree with that. Our aim should be to cause the minimal burden for users. However, if they want to try out an application or two, they ought to be able to run it. We can tell them to completely backup their .kde directory before doing so. Scenario: cp -a .kde .kde-backup apt-get install kmail-cvs <hmm, doesn't work good enough for me> apt-get install kmail That is, making most if not all _application_ packages mutually exclusive in their stable and cvs versions is sensible as you have said, but at least trying out stuff may be possible. And if they do an # apt-get install kde they should be able to get to a stable-only version. At any rate, the back-up thing is what they should be doing before trying out anything alpha and we should warn them about that issue. - -- Eray Ozkural (exa) <[EMAIL PROTECTED]> Comp. Sci. Dept., Bilkent University, Ankara www: http://www.cs.bilkent.edu.tr/~erayo GPG public key fingerprint: 360C 852F 88B0 A745 F31B EA0F 7C07 AE16 874D 539C -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE76x4cfAeuFodNU5wRAsH2AKCLQ7R8PNvOEd3x96r++GVI+kfyWgCffNRK IuKiEZXsU8Llpk5L5O2prlA= =E7C7 -----END PGP SIGNATURE-----
