https://bugzilla.novell.com/show_bug.cgi?id=466300
User alpar@cs.elte.hu added comment
https://bugzilla.novell.com/show_bug.cgi?id=466300#c6
--- Comment #6 from Alpar Juttner
Let me repeat, too: stop installing extensions from mercurial tarball "as default" if they are unsafe or unsupported.
It is a bit hard to argue if you twist my words in order to support your own agenda. If I'm saying it is "unsafe" to force everyone to use roller skates it does not mean that roller skates are "badly designed" or "buggy".
Regarding the packaging: my proposal is to split the packages into two (or more) parts, the core package and extension package(s). The extension packages can have own hgrc to enable it per installation.
This is a bad idea. - Firstly, it will not make anything better because if I want to use a certain extension, I must install the extension packages, then I will get a bunch of unwanted extensions turned on. It is especially a problem in multi user environments: if someone needs an extension at a point and ask the system admin to install it, then it will change the hg configuration of everyone. - Secondly, it will make things worse. Those extensions are that are shipped with mercurial are assumed _to be there_ (but turned off!!!) by default by all of the documentation, therefore so will do the users and third party tools. Even if you put every extension into a separate package, it will not solve the problems above: - In multiuser environment the extensions will be still either unavailable or turned on to everybody. - This would suggest that I should only have those extensions installed on my computer that I want to have to be turned on. But it means that I cannot change the config (e.g. turn on an extension temporally) when I'm offline. Anyway, I do not feel that it is easier to install (or remove) a package than to put a new line (or comment one line out) in the ~/.hgrc file. Especially, because - actually you cannot really use mercurial without having a custom config file (you must at least set your user name). - many extensions needs additional configuration in ~/.hgrc - enabling the needed extensions in ~/.hgrc before the use is what the documentation of mercurial itself and the documentation of each and every extension suggest.
If this approach is acceptable, I'll work on it for 11.2.
Please do not do that. The right solution is easy and is already in hand: simply do not hack the default global configuration of mercurial (i.e. do not switch the extensions on by default). As far as I heard, this is what the Debian packagers plan do, as well. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.