Below is the list of changes that have just been commited into a local
MyODBC 3.51 repository of 'pharvey'. When 'pharvey' does a push, they will
be propogaged to the main repository and within 2 hours after the push
into the public repository.
For more information on how to access the public repository see:
http://www.mysql.com/products/myodbc/faq_2.html#Development_ source
You can also browse the changes from public repository:
Complete repository: http://mysql.bkbits.net:8080/myodbc3/
This changeset : http://mysql.bkbits.net:8080/myodbc3/cset [at] 1.448
ChangeSet
1.448 05/01/30 21:18:12 peterh [at] mysql.com +3 -0
- tweeks to make 3.51.11-1 distro on Linux
util/Makefile.am
1.4 05/01/30 21:18:11 peterh [at] mysql.com +3 -0
- tweeks to make 3.51.11-1 distro on Linux
setup/Makefile.am
1.8 05/01/30 21:18:11 peterh [at] mysql.com +1 -2
- tweeks to make 3.51.11-1 distro on Linux
README.dist
1.3 05/01/30 21:18:11 peterh [at] mysql.com +34 -66
- tweeks to make 3.51.11-1 distro on Linux
# This is a BitKeeper patch. What follows are the unified diffs for the
# set of deltas contained in the patch. The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User: peterh
# Host: peter.peterharvey.org
# Root: /home/pharvey/SandBox/MySQL/myodbc-3.51
--- 1.2/README.dist Tue Oct 26 09:56:17 2004
+++ 1.3/README.dist Sun Jan 30 21:18:11 2005
[at] [at] -1,21 +1,24 [at] [at]
+----------------------------------------------------------- --+
-| MyODBC |
+| Connector/ODBC |
| Making Distributions |
+----------------------------------------------------------- --+
+<draft> <draft> <draft>
Linux
-Source tar-ball
+Source
+(tar-ball)
- bk clone
- change current ver to new ver in source/config files
-- make -f Makefile.cvs
+- make -f Makefile.bk
- ./configure
- make dist
- source tar-ball will be in current dir
-RPM's
+Binary
+(RPM)
- bk clone
- change current ver to new ver in source/config files
[at] [at] -30,70 +33,35 [at] [at]
- source RPM will be in /usr/src/packages/SRPMS
- binary RPM will be in /usr/src/packages/RPMS/i586
+XP
-<draft> <draft> <draft>
-
-
-INTRODUCTION
------------------------------------------------------------ ----
-
-You want to read this if you are interested in creating a source
-or binary distribution of MyODBC.
-
-What follows are my notes of my experience creating various types
-of MyODBC distributions on various platforms. In other words -
-making a Generally Available (GA) release of MyODBC suitable
-for the download area of the MySQL web-site.
-
-In this document I start from MyODBC sources as found in the
-MyODBC bitkeeper source code respository and end with the
-creation of a number of tar-balls, rpm, OSX Packages, and Windows
-installer.
-
-I expect this document to be of interest to MySQL developers,
-support persons, and engineers.
-
-Finally; please consider this to be a working document. If you
-notice that it has become out of date then please update it :)
-
+Source
+(zip)
-MySQL RELEASE PROCEDURE
------------------------------------------------------------ ----
+- create tar-ball
+- unpack tar-ball
+$ zip -r zip-file.zip dir-name
+
+Binary
+(Wise Installer)
+
+- cd util
+- qmake
+- nmake
+- cd ..\setup
+- qmake
+- nmake
+- cd ..\myodbcinst
+- qmake
+- nmake
+- cd ..\imyodbc
+- qmake
+- nmake
+- cd ..\win32
+- nmake
+- open wise project in wise folder
-You must have a clear understanding of the changes included in
-the new distribution and these should be documented.
-
-A message should be sent out stating that the MyODBC source
-code repository is frozen in preparation for a release. All
-departments should be aware of this. Engineering should be aware
-that they will be making a release GA and where they can find
-the distributions.
-
-Make the distributions and provide them to engineering. It is
-likely that engineering will actually be making the
-distributions but perhaps not someone with the authority to
-to make GA.
-
-Quality Assurance (QA) process is applied here. QA typically
-means that volunteers within the organization will try out
-the distribution but most importantly release should be run
-through standard test suite.
-
-Engineering should send notice to community and internally that
-a new release is GA.
-
-A message should be sent out stating that the MyODBC source
-is no longer frozen and normal development may continue.
-
-GETTING CODE
------------------------------------------------------------ ---
-
-Get the source code from the source code repository;
-
-$ bk clone bk-internal:/home/bk/myodbc-3.51 myodbc-3.51
-
-This will get the latest myodbc-3.51 sources.
+<draft> <draft> <draft>
-LINUX
------------------------------------------------------------ ---
+
--- 1.7/setup/Makefile.am Sun Nov 21 16:12:19 2004
+++ 1.8/setup/Makefile.am Sun Jan 30 21:18:11 2005
[at] [at] -113,7 +113,7 [at] [at]
libmyodbc3S_la_LDFLAGS = \
-export-dynamic \
- -export-symbols [at] srcdir [at] /myodbc3S.exp \
+ -export-symbols [at] srcdir [at] /myodbc3S.def \
-release [at] myodbc_version [at] \
-module
[at] [at] -143,7 +143,6 [at] [at]
MYODBCSetupDataSourceTab3d.h \
MYODBCSetupLineEdit.h \
myodbc3S.def \
- myodbc3S.exp \
SideImage.xpm \
TopImage.xpm \
MySQL-16.xpm \
--- 1.3/util/Makefile.am Fri Dec 17 11:51:30 2004
+++ 1.4/util/Makefile.am Sun Jan 30 21:18:11 2005
[at] [at] -6,6 +6,9 [at] [at]
MYODBCUtilAllocDriver.c \
MYODBCUtilClearDataSource.c \
MYODBCUtilClearDriver.c \
+ MYODBCUtilDefaultDataSource.c \
+ MYODBCUtilGetDataSourceNames.c \
+ MYODBCUtilGetDriverNames.c \
MYODBCUtilDSNExists.c \
MYODBCUtilFreeDataSource.c \
MYODBCUtilFreeDriver.c \
--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org
