search for: incompatibili

From: Johnny Hughes <mailing-lists at hughesjr.com> > MUCH more FOSS oriented I've been taking an informal survey on this for awhile now. I know the new, official acronym is Free and Open Source Software (FOSS). But even before that acronym was popular, I had long argued that Stallman's insistence on calling it "Free Software" when that could be confused with

On Wed, 1 Apr 2015, Prof Brian Ripley wrote: &gt; I would start by trying LANGUAGE=en , e.g. More specifically, you can use en_US or en_GB. Rich [...] ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?

...everyone is very focused on the timsieve daemon and they tend to require its protocol specifics. The only other implementation I got working is smartsieve. The others either crashed or produced protocol errors (i.e. sieveshell). I hope I can get more client implementations to work to ensure the incompatibilies are not my fault. I am very eager to know what you think about the sieve implementation ideas and what you think of the new managesieve patch. Regards, -- Stephan Bosch stephan at rename-it.nl

...ppear on the scene quite quickly. I do see some advantages for them though. By contrast, I have been very relieved that S4 classes have not posed a problem for my code that relies on "old" classes (totally unlike my experience with S-Plus) but any time changes are made that involve some incompatibilies with old code there should be some pause. In Hmisc and Design I reference several functions that were not exported from packages that now use namespaces. There is an elegant solution with the package:::function notation, but I have been unable to use this solution because I use one code base fo...

In http://www.freebsd.org/releases/7.0R/announce.html says Updating Existing Systems > An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes > a major version upgrade, so no matter which method you use to update > an older system you should reinstall any ports you have installed on > the machine. This will avoid binaries becoming linked to inconsistent > sets