Re: [RFC] cygport documentation
On Jun 13 16:53, Warren Young wrote: On 6/13/2013 13:50, Achim Gratz wrote: a tutorial or similarly styled explanation of how to use cygport, That, or a recipe format, or a FAQ format. That is, one that starts with how, rather than what. it would probably help if the manual was called a reference to tone the expectations accordingly. Agreed. The current HTML manual -- awesome as it is compared to the old README file -- relies on you know know what you're looking for already. The biggest holes remaining are the missing answers for questions of the form, How do I get Cygport to do X for me? It might also help to walk through several real cygport files: 1. A very basic one, such as one for an autotools based project that requires no patching and no special configuration. 2. A more complicated one showing how to do common things. You're in a much better position than me to define common, Yaakov, so I won't try. 3. One for a package with a seriously oddball build system, requiring that you override a lot of what cygport tries to do for you by default. Yes, that's what may keep people a bit from using cygport. A general howto section and a few examples would help a lot I think. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
Re: [RFU] sqlite3-3.7.17-3
On Jun 13 16:54, Warren Young wrote: Would someone flip this package from test to curr for me, please? Leave 3.7.16.2-1 as prev. Done. Do you want to keep 3.7.13-1? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
Re: [RFC] cygport documentation
Several people have mentioned changes they would like to see in cygport's documentation. I believe the stable APIs are all documented now, but what more would you like to see in the docs? I'd like to see an explanation and an example or two of what cygclasses are for.
[64bit RFU] Perl modules needed for Biber
Here are the packages discussed starting at
http://cygwin.com/ml/cygwin-apps/2013-06/msg00120.html
D=http://sanibeltranquility.com/cygwin/64bit/release
wget -x -nH --cut-dirs=3 \
${D}/perl-Business-ISBN/perl-Business-ISBN-2.06-1.tar.bz2\
${D}/perl-Business-ISBN/perl-Business-ISBN-2.06-1-src.tar.bz2\
${D}/perl-Business-ISBN/setup.hint\
${D}/perl-Business-ISBN-Data/perl-Business-ISBN-Data-20120719.001-1.tar.bz2\
${D}/perl-Business-ISBN-Data/perl-Business-ISBN-Data-20120719.001-1-src.tar.bz2\
${D}/perl-Business-ISBN-Data/setup.hint\
${D}/perl-Business-ISMN/perl-Business-ISMN-1.11-1.tar.bz2\
${D}/perl-Business-ISMN/perl-Business-ISMN-1.11-1-src.tar.bz2\
${D}/perl-Business-ISMN/setup.hint\
${D}/perl-Business-ISSN/perl-Business-ISSN-0.91-1.tar.bz2\
${D}/perl-Business-ISSN/perl-Business-ISSN-0.91-1-src.tar.bz2\
${D}/perl-Business-ISSN/setup.hint\
${D}/perl-Capture-Tiny/perl-Capture-Tiny-0.22-1.tar.bz2\
${D}/perl-Capture-Tiny/perl-Capture-Tiny-0.22-1-src.tar.bz2\
${D}/perl-Capture-Tiny/setup.hint\
${D}/perl-Config-AutoConf/perl-Config-AutoConf-0.22-1.tar.bz2\
${D}/perl-Config-AutoConf/perl-Config-AutoConf-0.22-1-src.tar.bz2\
${D}/perl-Config-AutoConf/setup.hint\
${D}/perl-Data-Compare/perl-Data-Compare-1.22-1.tar.bz2\
${D}/perl-Data-Compare/perl-Data-Compare-1.22-1-src.tar.bz2\
${D}/perl-Data-Compare/setup.hint\
${D}/perl-Data-Diver/perl-Data-Diver-1.0101-1.tar.bz2\
${D}/perl-Data-Diver/perl-Data-Diver-1.0101-1-src.tar.bz2\
${D}/perl-Data-Diver/setup.hint\
${D}/perl-Data-Dump/perl-Data-Dump-1.22-1.tar.bz2\
${D}/perl-Data-Dump/perl-Data-Dump-1.22-1-src.tar.bz2\
${D}/perl-Data-Dump/setup.hint\
${D}/perl-Date-Simple/perl-Date-Simple-3.03-1.tar.bz2\
${D}/perl-Date-Simple/perl-Date-Simple-3.03-1-src.tar.bz2\
${D}/perl-Date-Simple/setup.hint\
${D}/perl-Encode-EUCJPASCII/perl-Encode-EUCJPASCII-0.03-1.tar.bz2\
${D}/perl-Encode-EUCJPASCII/perl-Encode-EUCJPASCII-0.03-1-src.tar.bz2\
${D}/perl-Encode-EUCJPASCII/setup.hint\
${D}/perl-Encode-HanExtra/perl-Encode-HanExtra-0.23-1.tar.bz2\
${D}/perl-Encode-HanExtra/perl-Encode-HanExtra-0.23-1-src.tar.bz2\
${D}/perl-Encode-HanExtra/setup.hint\
${D}/perl-Encode-JIS2K/perl-Encode-JIS2K-0.02-1.tar.bz2\
${D}/perl-Encode-JIS2K/perl-Encode-JIS2K-0.02-1-src.tar.bz2\
${D}/perl-Encode-JIS2K/setup.hint\
${D}/perl-ExtUtils-LibBuilder/perl-ExtUtils-LibBuilder-0.04-1.tar.bz2\
${D}/perl-ExtUtils-LibBuilder/perl-ExtUtils-LibBuilder-0.04-1-src.tar.bz2\
${D}/perl-ExtUtils-LibBuilder/setup.hint\
${D}/perl-File-Find-Rule/perl-File-Find-Rule-0.33-1.tar.bz2\
${D}/perl-File-Find-Rule/perl-File-Find-Rule-0.33-1-src.tar.bz2\
${D}/perl-File-Find-Rule/setup.hint\
${D}/perl-File-Slurp/perl-File-Slurp-.19-1.tar.bz2\
${D}/perl-File-Slurp/perl-File-Slurp-.19-1-src.tar.bz2\
${D}/perl-File-Slurp/setup.hint\
${D}/perl-File-Slurp-Unicode/perl-File-Slurp-Unicode-0.7.1-1.tar.bz2\
${D}/perl-File-Slurp-Unicode/perl-File-Slurp-Unicode-0.7.1-1-src.tar.bz2\
${D}/perl-File-Slurp-Unicode/setup.hint\
${D}/perl-IO-HTML/perl-IO-HTML-1.00-1.tar.bz2\
${D}/perl-IO-HTML/perl-IO-HTML-1.00-1-src.tar.bz2\
${D}/perl-IO-HTML/setup.hint\
${D}/perl-IPC-Run3/perl-IPC-Run3-0.045-1.tar.bz2\
${D}/perl-IPC-Run3/perl-IPC-Run3-0.045-1-src.tar.bz2\
${D}/perl-IPC-Run3/setup.hint\
${D}/perl-List-AllUtils/perl-List-AllUtils-0.03-1.tar.bz2\
${D}/perl-List-AllUtils/perl-List-AllUtils-0.03-1-src.tar.bz2\
${D}/perl-List-AllUtils/setup.hint\
${D}/perl-List-MoreUtils/perl-List-MoreUtils-0.33-1.tar.bz2\
${D}/perl-List-MoreUtils/perl-List-MoreUtils-0.33-1-src.tar.bz2\
${D}/perl-List-MoreUtils/setup.hint\
${D}/perl-Log-Log4perl/perl-Log-Log4perl-1.41-1.tar.bz2\
${D}/perl-Log-Log4perl/perl-Log-Log4perl-1.41-1-src.tar.bz2\
${D}/perl-Log-Log4perl/setup.hint\
${D}/perl-LWP-Protocol-https/perl-LWP-Protocol-https-6.04-1.tar.bz2\
${D}/perl-LWP-Protocol-https/perl-LWP-Protocol-https-6.04-1-src.tar.bz2\
${D}/perl-LWP-Protocol-https/setup.hint\
${D}/perl-MIME-Charset/perl-MIME-Charset-1.009.3-1.tar.bz2\
${D}/perl-MIME-Charset/perl-MIME-Charset-1.009.3-1-src.tar.bz2\
${D}/perl-MIME-Charset/setup.hint\
${D}/perl-Mozilla-CA/perl-Mozilla-CA-20130114-1.tar.bz2\
${D}/perl-Mozilla-CA/perl-Mozilla-CA-20130114-1-src.tar.bz2\
${D}/perl-Mozilla-CA/setup.hint\
${D}/perl-Number-Compare/perl-Number-Compare-0.03-1.tar.bz2\
${D}/perl-Number-Compare/perl-Number-Compare-0.03-1-src.tar.bz2\
${D}/perl-Number-Compare/setup.hint\
${D}/perl-Readonly/perl-Readonly-1.03-1.tar.bz2\
${D}/perl-Readonly/perl-Readonly-1.03-1-src.tar.bz2\
${D}/perl-Readonly/setup.hint\
${D}/perl-Readonly-XS/perl-Readonly-XS-1.05-1.tar.bz2\
${D}/perl-Readonly-XS/perl-Readonly-XS-1.05-1-src.tar.bz2\
${D}/perl-Readonly-XS/setup.hint\
${D}/perl-Regexp-Common/perl-Regexp-Common-2013031301-1.tar.bz2\
${D}/perl-Regexp-Common/perl-Regexp-Common-2013031301-1-src.tar.bz2\
${D}/perl-Regexp-Common/setup.hint\
[64bit RFU] biber-1.5.1
New package (64bit only until perl_vendor goes away or gets updated on
32bit Cygwin):
D=http://sanibeltranquility.com/cygwin/64bit/release
wget -x -nH --cut-dirs=3 \
${D}/biber/biber-1.5-1.tar.bz2 \
${D}/biber/biber-1.5-1-src.tar.bz2 \
${D}/biber/setup.hint
Thanks.
Ken
[64bit RFU] texlive-collection-bibtexextra-20130529-2
This is a downgrade of biblatex from version 2.6 to 2.5 for
compatibility with biber-1.5
D=http://sanibeltranquility.com/cygwin/64bit/release/TeX
TL=texlive
TC=texlive-collection
wget -x -nH --cut-dirs=3 \
${D}/${TC}-bibtexextra/${TC}-bibtexextra-20130529-2.tar.bz2\
${D}/${TC}-bibtexextra/${TC}-bibtexextra-20130529-2-src.tar.bz2\
${D}/${TC}-bibtexextra/setup.hint
Thanks.
Ken
Re: [RFU] sqlite3-3.7.17-3
On 6/14/2013 01:54, Corinna Vinschen wrote: On Jun 13 16:54, Warren Young wrote: Would someone flip this package from test to curr for me, please? Leave 3.7.16.2-1 as prev. Done. Thanks! Do you want to keep 3.7.13-1? I didn't know I could have more than one prev. Sure, let's keep it a while. Just in this past week, I got a complaint about one of the changes in .16.2 relative to .13, so it's conceivable some may want to step back two steps if .17 doesn't work out for everyone.
Re: [64bit] Biber packaging questions
On Wed, Jun 12, 2013 at 10:18 AM, Corinna Vinschen wrote: On Jun 12 10:10, Ken Brown wrote: Here are my questions: 1. Should these build prerequisites be added to the 64bit distro? Otherwise it will be difficult for others to rebuild biber from source. In theory, yes. Ideally for 32 and 64 bit, even if you don't really need it for 32 bit. 2. Biber requires perl 5.16 or later, so I did a quick and dirty build of perl-5.16.3. By quick and dirty I mean that I simply took Yaakov's perl.cygport and removed all patches that wouldn't apply. This is no problem for *users* of biber.exe, since the latter includes the perl DLL. But again it makes it difficult for others to replicate the build until the official perl is updated. I have no idea what to do about this. AFAIR Reini wrote something about perl 5.16 having some serious bugs, or problems which makes it unfeasible for the distro. Reini, can you chime in here? With enabling unicode symbols 5.16 silently started allowing \0 in symbol and package names, without any protection and further support, which makes it unusable for me in serious environments. Since I'm not considering cygwin a serious environment it's probably no big deal. Unfortunately p5p and the security team is in denial and ignores the issues involved. I'm favoring 5.18, and started writing the patches. It will probably be 5.18.1-1. I found nothing critical so far. Just minor Time::HiRes and alarm problems (we are too slow), stat, a new regex regression, some new Storable problems. And mainly discspace problems with my win8 64bit vm. As if 17GB is not enough. Failed 8 tests out of 2338, 99.66% okay. ../cpan/CGI/t/tmpdir.t ../cpan/Time-HiRes/t/alarm.t ../cpan/Time-HiRes/t/ualarm.t ../ext/XS-APItest/t/call_checker.t ../lib/File/stat.t ../lib/locale.t op/filetest.t op/stat.t 3. There is a completely different approach I could take. Namely, I could simply package Biber as a perl module and forget about packing it into a Perl Archive. If I do this, then users will need perl 5.16 or later, as well as most or all of the perl modules listed above, so the RFU will have to wait for a perl update; but that's probably not serious. Would this be preferable? I'm not aware of any Linux distros that do this, though someone did do it unofficially for Fedora: http://www.linux.cz/pipermail/texlive/2012-August/000563.html I would say that's up to you, but it doesn't really sound like the right thing to do. I would also favor using biber as non-packaged perl script. Since you need so many perl deps, do you really want to keep them seperate? I would just bundle them to something like a perl-biber-bundle package, into vendor_perl. -- Reini Urban http://cpanel.net/ http://www.perl-compiler.org/
Re: [64bit RFU] Perl modules needed for Biber
On Jun 14 13:34, Ken Brown wrote: Here are the packages discussed starting at http://cygwin.com/ml/cygwin-apps/2013-06/msg00120.html D=http://sanibeltranquility.com/cygwin/64bit/release wget -x -nH --cut-dirs=3 \ [...] Uploaded. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
Re: [64bit RFU] biber-1.5.1
On Jun 14 13:43, Ken Brown wrote:
New package (64bit only until perl_vendor goes away or gets updated
on 32bit Cygwin):
D=http://sanibeltranquility.com/cygwin/64bit/release
wget -x -nH --cut-dirs=3 \
${D}/biber/biber-1.5-1.tar.bz2 \
${D}/biber/biber-1.5-1-src.tar.bz2 \
${D}/biber/setup.hint
Uploaded.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[RFU] perl-Text-CSV-1.32-1
These /ought/ to be architecture independent, but just in case:
# 32-bit:
BASEURL=https://dl.dropbox.com/sh/7y1yn4whbyho9a7
wget --no-check-certificate --no-host-directories --force-directories
--cut-dirs=4 \
${BASEURL}/7XsQJwdP8f/release/perl/perl-Text-CSV/perl-Text-CSV-1.32-1-src.tar.bz2
\
${BASEURL}/STcg5Szw-O/release/perl/perl-Text-CSV/perl-Text-CSV-1.32-1.tar.bz2
\
${BASEURL}/uVaNvKwqAl/release/perl/perl-Text-CSV/setup.hint
# 64-bit:
BASEURL=https://dl.dropbox.com/sh/7y1yn4whbyho9a7
wget --no-check-certificate --no-host-directories --force-directories
--cut-dirs=6 \
${BASEURL}/J-Cd5xee9X/64bit/release/perl/perl-Text-CSV/perl-Text-CSV-1.32-1-src.tar.bz2
\
${BASEURL}/PIoGpKTCPa/64bit/release/perl/perl-Text-CSV/perl-Text-CSV-1.32-1.tar.bz2
\
${BASEURL}/kX7mDjmu-S/64bit/release/perl/perl-Text-CSV/setup.hint
In both cases, please leave 1.21-1 as previous.
Many thanks in advance,
Dave.
Re: [64bit] Biber packaging questions
On 2013-06-14 13:37, Reini Urban wrote: Since you need so many perl deps, do you really want to keep them seperate? Yes. I would just bundle them to something like a perl-biber-bundle package, into vendor_perl. No, perl_vendor needs to go away, not get bigger. Yaakov
Re: [64bit] Biber packaging questions
Reini Urban writes: I would also favor using biber as non-packaged perl script. +1 Since you need so many perl deps, do you really want to keep them seperate? Yes, I would want _all_ non-core Perl distributions as separate cygwin packages. That's the only sane way to deal with these when the need for local patches arises. This is admittedly rare, but it does happen. I would just bundle them to something like a perl-biber-bundle package, into vendor_perl. May I suggest to name all bundle packages perl_* (underscore) so they differ from the distribution packages? And again the bundles should just list the dependencies, while the actual distributions are in their own packages. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
Re: [64bit] Biber packaging questions
On Fri, Jun 14, 2013 at 1:49 PM, Yaakov (Cygwin/X) wrote: On 2013-06-14 13:37, Reini Urban wrote: I would just bundle them to something like a perl-biber-bundle package, into vendor_perl. No, perl_vendor needs to go away, not get bigger. I said vendor_perl, the location. You meant perl_vendor the package. Achim: Since you need so many perl deps, do you really want to keep them seperate? Yes, I would want _all_ non-core Perl distributions as separate cygwin packages. That's the only sane way to deal with these when the need for local patches arises. This is admittedly rare, but it does happen. If you really want to maintain 2000+ packages do it. I don't care. I hope you know what happens over at debian, macports and redhat with this scheme. Been there, done that. Also, our UI setup selector cannot handle that. At cygwin we favor cpan over cygwin packages. If the urgent need for a local patch arises the user can always cpan it, until the lazy maintainer updates his package. -- Reini Urban http://cpanel.net/ http://www.perl-compiler.org/
