Hi Yaakov,
When we discussed folding features from my previously forked cygport into
upstream back in January, the need to do so was pretty much pre-empted when
Chuck released the gcc-tools packages, but there was one aspect of it that got
dropped on the floor. GCC uses a forked libtool, and because of
default_excludes, my local patches to it get lost every time I run the
packaging step and I keep on having to manually re-add them. The simplest
solution is to just add gcc to the list of packages for which we don't add
ltmain.sh (et al.) to the default_excludes.
* bin/cygport.in (__pkg_diff): Don't set default_excludes for
GCC[34]*.
Ok? (I generated this against installed cygport-0.9.7-1, but it looks like
it should apply ok to SVN without even needing any --fuzz).
cheers,
DaveK
--- cygport.orig 2009-07-07 16:03:50.265625000 +0100
+++ cygport 2009-07-07 16:06:08.468750000 +0100
@@ -1734,7 +1734,7 @@ __pkg_diff() {
*.class *.jlc *.pyc *.mo *.gmo *.orig *.rej *.spec *.temp *~ *.stackdump";
case ${PN} in
- automake*|libtool) ;;
+ automake*|libtool|gcc[34]*) ;;
*) default_excludes+=" COPYING INSTALL compile config-ml.in \
config.guess config.sub depcomp elisp-comp install-sh \
libtool.m4 ltoptions.m4 ltsugar.m4 ltversion.m4 lt~obsolete.m4 \
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/blackberry
_______________________________________________
Cygwin-ports-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cygwin-ports-general
