Op Mon, 14 Feb 2005 10:16:08 -0500 schreef Christopher Faylor
in <[EMAIL PROTECTED]>:
: On Mon, Feb 14, 2005 at 09:54:41AM -0500, Dick Repasky wrote:
: > Every so often a query surfaces about cygwin dll version compatibility.
[...]
: > The recommendations are:
: >
: > 1) Use a distinctly named shared memory area in the cygwin dll.
: > 2) Use a distinctly named registry key for storing cygwin file system
: > mount points.
: > 3) Identify the origin of the cygwin dll in the cygwin dll.
[...]
: If you are a 3rd party distributor, you should check for existing
: installations of the dll. If the existing version of cygwin DLL is the
: same or newer than the one you want to use, then notify the user that
: there is already a version on the system and that you will not be
: installing a new version.
:
: Otherwise, install your version in a standard location so that it will
: survive being upgraded if a user decides to upgrade.
:
: And, of course, unless this is a distribution which is internal to your
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
: organization, remember to offer the user the source code to whatever
^^^^^^^^^^^^
: application you're providing to them.
Where did you find this exception? I don't recall seeing it in the GPL.
(I'm a member of the organization of all beings, aren't you as well?)
[...]
L8r,
Buzz. [TITT[TL]L]
--
) | | ---/ ---/ Yes, this | This message consists of true | I do not
-- | | / / really is | and false bits entirely. | mail for
) | | / / a 72 by 4 +-------------------------------+ any1 but
-- \--| /--- /--- .sigfile. | |perl -pe "s.u(z)\1.as." | me. 4^re
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
