> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Ludek Finstrle
> Sent: 19 December 2005 08:04
> To: Peter Eisentraut
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] psqlODBC 8.01.0105 Development snapshot
> > > I announce new development snapshot with this informations:
> > > Release Name: psqlodbc 8.01.0105
> > Um, it might be nice of you create a CVS tag for snapshot
> releases (as
> It's not compiled from CVS only. There is some patches which isn't
> commited yet. May I still create CVS tag?
No. CVS tags must match what is actually released.
> > was done in the past) and if you provided the source code
> > This is "open source" software after all. And making binary only
> > releases might also be considered a license violation.
> I think all patches goes through pgsql-odbc mailing list so if anyone
> would get the source he can. I don't think over a license violation.
> If you think it's license violation I have to remove older dev
> snapshots (it's too time consuming to get source for it) and I'll add
> source code for latest dev snapshot).
> What's your opinion?
I think Peter's being a little over cautious. There have been psqlODBC
snapshots released without source releases right back to when Byron was
maintaining it years ago. They are 'official' project snapshots, built
for testing purposes by the primary copyright holders (PGDG) and
released onto the project site which hosts the source repository. AFAICR
I'm the only one who ever did release source tarballs with snapshots.
The easy way to be sure though, is to just zip up the source tree and
upload it with the binaries, or better yet, build a tarball on a Unix
box or in Msys and upload that.
pgsql-odbc by date
|Next:||From: Freeking Wu||Date: 2005-12-19 12:45:28|
|Subject: insert and update in vb.net|
|Previous:||From: Ludek Finstrle||Date: 2005-12-19 08:09:08|
|Subject: Re: MyLog file for #1000457 issue "Autocommit and Cancel"|