Re: python 2.2 -> python 2.3 transition
On Sun, Aug 17, 2003 at 11:22:43AM +0200, Torsten Landschoff wrote: | On Wed, Aug 13, 2003 at 08:33:26AM -0500, John Goerzen wrote: | > Now, I could do the dependency on python (>= 2.2), python (<<2.3) thing. | > But what would that gain me or users? I see no benefit there, other than | > people tracking sid would find OfflineIMAP uninstallable until it gets | > updated to depend on Python 2.3. | > | > There are plenty of OfflineIMAP users that don't use Python themselves, | > don't care that it's written in Python -- and probably some that don't | > *know* it's written in Python. | > | > (And yes, the bang path explicitly calls python2.2) If the program explicitly calls python2.2, then it should depend on python2.2, not python (2.2). The usefulness of depending on the default python is (IMO) geared for libraries. wxPython is just one example. This allows an admin to install the library for the default python and not have to worry about package name changes when the default python changes. (IMO the libraries _should_ also provide versions for the other currently available python versions, if possible/feasible) | The dependency on python (>= 2.2), python (<< 2.3) is for the case where | you have a module which loads into python and supports only a single | python version. | | After python changed you can't install that package (wxgtk-python or | whatever) anymore. The positive effect for the users is that you can't | upgrade python while wxgtk-python is installed so your system won't | break. The negative effect for the users is that you can't upgrade python while wxgtk-python is installed so you can't try out the latest-and-greatest python in the meantime. This is the issue at hand. -D -- For society, it's probably a good thing that engineers value function over appearance. For example, you wouldn't want engineers to build nuclear power plants that only _look_ like they would keep all the radiation inside. (Scott Adams - The Dilbert principle) http://dman13.dyndns.org/~dman/ pgpiUSHgB0y5j.pgp Description: PGP signature
Re: VIM features
On Tue, Jan 01, 2002 at 01:54:15PM +0100, Eduard Bloch wrote: | Hello, | | I would like to see more user feedback on Debian's settings of the | VIM editor. Currently, two important features are disabled in the | default configurations: Syntax highlighting and special intending | schemes. The question is: why? I think you'll have to ask the package maintainer about that. ([EMAIL PROTECTED]). | Some (influent) people want to make VIM behave as the "normal" vi. | But does this make sense? It does, depending on the environment. If many users of a system have used "normal" vi for a long time, and you want to convince them to install vim instead, it better behave the way they expect. You can, of course, configure it as you like while the other users stick with the traditional behavior. | VIM is either installed as the "default" | vi, nor does it have more priority in the "alternatives" entry. | Additionaly, many packages suggest nvi, so it is often installed as the | first vi editor and people often do not come in touch with vim. In this environment perhaps it doesn't make sense to default to compatibility settings. | NOTE: this is not a start of a new holy war. I do not ask for giving | vim's alternatives-entry a higher priority or so. I just want to use all | VIM's features when I initially install it, without looking into my | big config to enable intending or editing the vimrc file to enable | highlighting. My .vimrc is big enough already with autocommands for various filetypes and the like. I move it around with me to whichever systems I use, so for me it is not a big deal. -D -- A Microsoft Certified System Engineer is to information technology as a McDonalds Certified Food Specialist is to the culinary arts. Michael Bacarella commenting on the limited value of certification.
Re: Debian installer
On Mon, Dec 31, 2001 at 10:20:14PM +1100, Penguin wrote: | How does it work? Broad overview: does it install a root filesystem and | simply do a huge cp /mnt/cdrom/package /wherever then configure, or what? It depends on what you tell it to do. It does all the basic setup of a system (partition tables, keyboard type, etc) and puts a base system on the partition you specify. The base system is enough to boot up, file management, and install additional packages. -D -- If your company is not involved in something called "ISO 9000" you probably have no idea what it is. If your company _is_ involved in ISO 9000 then you definitely have no idea what it is. (Scott Adams - The Dilbert principle)
