Mail Archives: cygwin/2012/06/05/02:07:41
--------------090507070505070104000109
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 6/4/2012 2:11 AM, Achim Gratz wrote:
>
> There's a new version for SQlite3 released. I've put the fix in the source
> patch now and removed the define from the CPPFLAGS, also ignoring sqlite3.pc for
> the diff.
Thanks, Achim. See my RFU message on the -apps list if you want to try
the packages in advance of them hitting the mirrors.
I changed your .cygport file considerably. Partly that's just style
issues, but it also has to do with my build procedure. You might be
interested: the attached cygport-new script makes creating a new version
pretty easy:
1. Put my sqlite3.cygport file and src.patch in a work directory.
2. Run 'cygport-new 3.7.12.1'. It assumes -1 if you don't give a
package revision number.
3. If nothing changed incompatibly, you're done; upload and send RFU
message. Else, fix the problem and goto 2.
Then for each new release you want to package, you try starting with
step 2, passing the new version number. If that fails, you usually have
to go back to step 1 and edit the .cygport or .patch file.
You're welcome to take these tools and maintainership of the package.
The only reason I maintain it is that its previous maintainer went MIA
and it was going to be dropped from the distro; I rescued it purely
because I knew what sqlite was and had some idea how to build and test
it. I don't actually use it on Cygwin like you do[*], so I'm not well
motivated to keep it up to date. I mainly react to bug reports like
yours. And as you see, not always promptly. :)
[*] I mainly use sqlite3 on other platforms, and then via other software
that happens to use it. Firefox, lots of stuff on OS X, Adobe Flex and
Lightroom...
--------------090507070505070104000109
Content-Type: text/plain; charset=windows-1252;
name="cygport-new"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="cygport-new"
#!/bin/bash
if [ -n "$1" ]
then
if [ `echo $1 | tr -d -` = "$1" ]
then
version="$1-1"
echo Assuming you meant version $version
else
version="$1"
fi
cwd=`pwd`
pkgname=`basename $cwd`
base=$pkgname-$version
set -x
if [ -e src.patch ] ; then cp -f src.patch $base.src.patch ; fi
cp -f $pkgname.cygport $base.cygport
cygport $base.cygport download
cygport $base.cygport prep
cp README *.hint $base/CYGWIN-PATCHES
cygport $base.cygport compile &&
cygport $base.cygport install &&
cygport $base.cygport package &&
tar xjf $base-src.tar.bz2
else
echo usage: $0 version-number
echo
echo "Wraps up the steps involved in starting a new version of a"
echo "cygport effort. Does the prep through package steps, stopping"
echo "at the first error. This will probably be in 'compile', for"
echo "the first run-through."
echo
exit 1
fi
--------------090507070505070104000109
Content-Type: text/plain; charset=us-ascii
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
--------------090507070505070104000109--
- Raw text -