On 01/02/2022 19:22, Corinna Vinschen wrote:
Hi Jon,
On Feb 1 17:25, Jon Turney wrote:
Be more careful not to remove an existing .gnu_debuglink, even if we
think this package has no useful debug symbols.
(Some versions of 'llvm-objdump -l' fail to find line number info even
though it's there.
Yaakov,
to avoid the never ending loop due to readlink mismatch
with some paths.
I will really appreciate.
Regards
Marco
--- src_postinst.cygpart_orig 2014-12-11 21:29:07.958761300 +0100
+++ src_postinst.cygpart2014-12-11 21:29:40.113806600 +0100
@@ -1297,7 +1297,7 @@
Reini Urban writes:
> Looks a bit weird. Don't we have a better field for this cpan quirks?
> Like a new CPAN_DIR which defaults to CPAN_AUTHOR?
I've just added an alternative configuration variable CPAN_DIR that
records just the directory component and sent the patch (together with a
few more to
Reini Urban writes:
> Just for easier understanding:
> How would that look like for e.g.
> A/AM/AMBS/Inline/Inline-Files-0.68.tar.gz
>
> NAME=Inline-Files
> inherit perl
> CPAN_AUTHOR=AMBS/Inline
Yes, exactly.
> Looks a bit weird.
Well, that's the author's choice…. Looks much less wierd to me
On 09/26/2012 06:51 AM, Achim Gratz wrote:
Hi Yaakov,
several Perl distributions have chosen to put the actual archives in a
subdirectory (e.g. Inline::Files). So far I've dealt with those by editing
SRC_URI after "inherit perl", but I'd like something more straigtforward. I
propose that CPAN
Hi Yaakov,
several Perl distributions have chosen to put the actual archives in a
subdirectory (e.g. Inline::Files). So far I've dealt with those by editing
SRC_URI after "inherit perl", but I'd like something more straigtforward. I
propose that CPAN_AUTHOR should optionally include this additi
The cygport 0.3.8 "default_excludes" list is not suitable for all
projects, in particular when aclocal.m4 is used in a non-automake
project like bash (http://sourceware.org/ml/cygwin/2007-03/msg00613.html).
With the attached, the default_excludes list is cleared when when
DIFF_EXCLUDES starts
Forward port to latest release.
For further history and justifiation of this patch, see
http://cygwin.com/ml/cygwin/2007-01/msg00114.html and follow the
embedded links and threads.
--
Chuck
2007-02-05 Charles Wilson <...>
* bin/dorelsym: new file.
* bin/Makefile.am: add new
Forward port to latest release.
For further history and justifiation of this patch, see
http://cygwin.com/ml/cygwin/2007-01/msg00113.html and follow the
embedded links and threads.
--
Chuck
2007-02-05 Charles Wilson <...>
* bin/cygport.in (custom_dummy_core): new function, used to
Forward port to latest release.
For further history and justifiation of this patch, see
http://cygwin.com/ml/cygwin/2007-01/msg00112.html and follow the
embedded links and threads.
--
Chuck
2007-02-05 Charles Wilson <...>
* bin/prep_gnu_info.sh: allow cygport client to suppress
Forward port to latest release.
For further history and justifiation of this patch, see
http://cygwin.com/ml/cygwin/2007-01/msg00111.html and follow the
embedded links and threads.
--
Chuck
2007-02-05 Charles Wilson <...>
* bin/cygport.in (src_fetch_auto): new function refactored
Forward port to latest release. Only change from previous, is that
current cygport CVS now checks for ${SRCDIR} before cd'ing into it, so
that part of the previous patch has been removed, below.
For further history and justifiation of this patch, see
http://cygwin.com/ml/cygwin/2007-01/msg0011
Yaakov (Cygwin Ports) wrote:
Could you please provide a sample .cygport showing what would be
accomplished with this?
Well, there's the src_prep_init|fini_hook example used in the
jpeg.cygport (from the mixed-mode-demo tarball). Again, the extra
SRC_URIs are all unpacked automatically by cyg
Charles Wilson wrote:
If THAT doesn't exercise the mixed-mode patch, nothin' will.
Except that it also uses the src_prep_init_hook changes. Which only
makes sense: if you download third-party or upstream patches, somehow
you've got to "do" something with them. PATCH_URI helps, but in this
Yaakov (Cygwin Ports) wrote:
Could you provide a sample .cygport (and .src.patch if necessary) which
I could use for testing this feature? (In general, for these major
patches this would be helpful.)
http://cygutils.fruitbat.org/ITP/mixed-mode-demo.tar.bz2
contains
jpeg-6b-12.cygport
jpeg-6b-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
> [implementation details]
> [1] Possibiliyt: remove the readonly protection on the existing,
> internal, automation functions (like __prep_installdir or src_prep).
> This is a really bad idea: some of these functions (especiall
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
> ...and allow the new PATCH_URI in cygport-0.2.7 to work when main src is
> in CVS|SVN|GIT repo. (At present, in 0.2.7, PATCH_URI is ignored if
> inherit cvs|svn|git).
True, only because I haven't yet had such a case.
> With
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
> * bin/cygport.in: use --datarootdir in preference
> to --datadir/--infodir/--mandir when using
> autoconf-2.60 and later.
Thanks. Fixed in CVS.
> * autogen.sh: Ensure that autoconf will not complain
> wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
> The recent change in apply_patch has a small bug, fixed by the attached.
>
> 2006-01-05 Charles Wilson <...>
>
> * bin/cygport.in (apply_patch): use correct variable name
Thanks. Fixed in CVS.
Yaakov
-BEGIN PGP
The recent change in apply_patch has a small bug, fixed by the attached.
2006-01-05 Charles Wilson <...>
* bin/cygport.in (apply_patch): use correct variable name
--
Chuck
--- bin/cygport.in 2007-01-06 00:30:50.59375 -0500
+++ bin/cygport.in 2007-01-06 04:26:46.09375
...patch withdrawn. It's the least *generally* useful, and most
invasive, of all of my patches, and at present applies to only two
packages in the cygwin universe, both of which I maintain -- and it only
applies when those packages are compiled in a non-standard way.
I'll update the patch the
Split out from my relocatable patch, because I think this is a useful
tool for other (non-relocatable) cygports. Because the patch creates a
new script, after applying the patch, don't forget to:
(1) chmod +x bin/dorelsym
(2) cvs add bin/dorelsym
What it does:
dorelsym creates symlink to
Implements an extensible method of calling custom cygport functions from
the cygport command line, in addition to the existing prep, install,
check, pkg ones (etc). This is a forward port of the original patch,
posted on 2006-12-9 here:
http://www.cygwin.com/ml/cygwin/2006-12/msg00366.html
I
Originally part of the relocatable patch from 2006-10-22:
http://www.cygwin.com/ml/cygwin/2006-10/msg00743.html
On 2006-11-28, split into its own patch when I refactored all my cygport
patches after cygport-0.2.6 was released:
http://www.cygwin.com/ml/cygwin/2006-11/msg00719.html
Now that cygp
...and allow the new PATCH_URI in cygport-0.2.7 to work when main src is
in CVS|SVN|GIT repo. (At present, in 0.2.7, PATCH_URI is ignored if
inherit cvs|svn|git).
Admittedly, that is be an odd situation: an "official" patch that is
supposed to be applied to a CVS checkout -- if it is "officia
Cygport automates many of the tedious steps of the build process for
cygwin ports (and that's a GOOD thing). However, at present there are
cases when the existing customization/extension points provided by
cygport are not sufficient -- the user needs to intervene
before/after/during some of th
Two minor changes missed in 0.2.7's ac2.61 support:
(1) prefer --datarootdir for ac2.60 *and above*, not just ac2.60
(2) automake-1.10's aclocal inserts more stringent error checking
for autoconf version mismatch into aclocal.m4. This error
checking cause autoreconf to complain
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
find ${B} -type f -exec touch -t $(date +%Y%m%d%H%M.%S) '{}' +;
Which version of find? I know there was an upstream bug report to
findutils that 'find -exec {} +' was not sharing the same logic as xargs
in 4.3.0, but that was supposed to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Charles Wilson on 11/15/2006 12:37 AM:
> Usually, the 'find ... -exec cmd ...' idiom makes a lot of sense -- it's
> faster, one fewer forks (maybe MANY fewer), etc.
>
> However, you sometimes run into troubles with extremely long filelist
Usually, the 'find ... -exec cmd ...' idiom makes a lot of sense -- it's
faster, one fewer forks (maybe MANY fewer), etc.
However, you sometimes run into troubles with extremely long filelists.
As I did with ncurses (1183 files in the build/ directory) -- and I got
a 'too many files' error fro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Wilson wrote:
> At present, if you use cvs|svn|git cygclass, you can only have one
> SRC_URI. This patch does three related things
>
> These changes were necessary to support building jpeg (using the
> autotoolized source package at sourceforg
At present, if you use cvs|svn|git cygclass, you can only have one
SRC_URI. This patch does three related things
(1) relaxes that restriction slightly. Now, the *first* SRC_URI
corresponds to the tarball created from the remote repository checkout
via CVS_URI/SVN_URI/GIT_URI. The other en
Yaakov S (Cygwin Ports) wrote:
Charles Wilson wrote:
| The attached patch (+ two new files) enables cygport to build
| "relocatable" packages using the framework devised by Bruno Haible -- if
| the upstream source supports it. Currently, only libiconv and gettext
| support this feature (coincide
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Wilson wrote:
| The attached patch (+ two new files) enables cygport to build
| "relocatable" packages using the framework devised by Bruno Haible -- if
| the upstream source supports it. Currently, only libiconv and gettext
| support this fe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Wilson wrote:
> The attached patch (+ two new files) enables cygport to build
> "relocatable" packages using the framework devised by Bruno Haible -- if
> the upstream source supports it. Currently, only libiconv and gettext
> support this fea
The attached patch (+ two new files) enables cygport to build
"relocatable" packages using the framework devised by Bruno Haible -- if
the upstream source supports it. Currently, only libiconv and gettext
support this feature (coincidentally, the upstream maintainer of both
packages is...Bruno
36 matches
Mail list logo
