Re: VCLZip Pro 3.04

From: Davids (nowhere_at_nowthere.com)
Date: 01/19/04


Date: Mon, 19 Jan 2004 12:52:18 -0700

Your position is untenable, at best. Your implication is that if Microsoft
bought up this package and bundled it as part of Windows, then it would be OK
for you to use it?

I too work in an academic research environment, and while we develop and release
a large body of code to the research community, our choice was to NOT release
source code because we didn't want to have to deal with supporting it. This is
NOT an "open source" development effort, it is a controlled development
environment where we make sure that what goes into the code base is based on
sound science and established research, not some jokers who think the latest
trick algorithm might be useful to people who need to get reliable results.

Another David.

Alan Garny wrote:

> "David J Taylor" <davidtaylor@writeme.com.not-this-bit> wrote in message
> news:40066782$1@newsgroups.borland.com...
> > > Anyway, that's not the point. I am developing a software that I make
> > > available for free and with source code to the scientific community in
> > which
> > > I am involved in. From there, I canNOT have one bit of code for which I
> > > cannot provide the source code.
> > You don't provide the source code for the OS on which your applications
> > run, so what's different about "just one more DLL"?
>
> The difference is that by having the whole source code, my users can
> recompile the whole project without any problem (as long as they have D7,
> which is the only requirement), after having modified it, if they wanted to.
> I guess there is a bit of background to this decision of mine. Namely that I
> have been using scientific softwares in the past that have generated results
> that I couldn't explain to myself. From there, I wish I had had the
> opportunity to check the code. As a matter of fact, in one occasion I could
> just do that and found out that there were indeed some bugs... That's the
> reason I have decided to make my software open source and for that reason,
> it means that any 3rd party package I use must be open source too.
>
> In other words, I cannot use VCLZip or any commercial package, because
> should I decide to use it, I wouldn't be allowed to distribute it (which is
> fair enough). My users would have to buy it in order to recompile my
> application, should they wish to do so. Therefore, as it stands, it's not an
> option in my opinion.
>
> Alan.



Relevant Pages

  • Re: legal Q about masm
    ... > source code available to their customers for some reason? ... on open source, open source doesn't imply that the software is free for any ... in the file and release the new source code under GPL -- perfectly legal ... they're largely developing Win32 apps with MASM. ...
    (alt.lang.asm)
  • Re: cobbling a ComboBox
    ... suggest you have a look at the library source code (of Swing, ... package scratch; ... boolean shouldValidate = false; ... the String ought to be "scratch.CustomMetalComboBoxUI". ...
    (comp.lang.java.gui)
  • Re: Redhat and OpenSSL Manner
    ... It's equivalent to 0.9.7a as originally distributed by OpenSSL project, with security and bug fixes added to it by Red Hat. ... enhancements and new features might be backported from newer versions too if they are not introducing any compatibility problems (for example this is often done for kernel package in RHEL to support new hardware). ... If you look into the SRPM packages, you'll see that they contain original unchanged source code wich is the same version as the package version, and also bunch of patches that get applied to that source code prior to compilation. ...
    (RedHat)
  • Re: Linux Vs. FreeBSD
    ... > source code is annoyingly slow and relatively difficult when it cones ... > Elaborating on the whole binary compatibility thing, ... A better example would be Fedora ... You usually can't install a Fedora package on Suse or vice ...
    (comp.os.linux.misc)
  • Re: Linux Vs. FreeBSD
    ... > source code is annoyingly slow and relatively difficult when it cones ... > Elaborating on the whole binary compatibility thing, ... > install something intended for one distro on another, ... You usually can't install a Fedora package on Suse or vice ...
    (comp.os.linux.misc)