It's that time of decade again...time for me to patch setup.exe again.
But oh noes! The README instructions are wrong, and the program doesn't
build correctly from a fresh checkout. Hafta fix that first.
1. The README implies that you need automake 1.9 and libtool 1.5,
exactly. I didn't
On 9/12/2012 9:28 PM, Christopher Faylor wrote:
If you're going to do that you really should (re)learn how to submit a
proper patch. A patch uses diff -u format and contains a ChangeLog.
It's been a decade since I last used cvs diff. I forgot that it
doesn't include -u, since svn diff does
-u -p -r2.780 ChangeLog
--- ChangeLog 4 Sep 2012 13:55:16 - 2.780
+++ ChangeLog 13 Sep 2012 04:32:13 -
@@ -1,3 +1,13 @@
+2012-09-12 Warren Young war...@etr-usa.com
+
+ Sorting select packages UI lists case-insensitively now,
+ instead of taking setup.ini order, which is ASCIIbetical
On 9/7/2012 5:07 PM, Erwin Waterlander wrote:
Warren Young schreef, Op 8-9-2012 0:00:
On 9/7/2012 2:14 PM, Erwin Waterlander wrote:
For Cygwin the commands 'd2u' and 'u2d' have been added.
??
$ which d2u
/usr/bin/d2u
$ cygcheck -f /usr/bin/d2u
dos2unix-6.0.1-1
So what does
On 9/7/2012 2:14 PM, Erwin Waterlander wrote:
For Cygwin the commands 'd2u' and 'u2d' have been added.
??
$ which d2u
/usr/bin/d2u
$ cygcheck -f /usr/bin/d2u
dos2unix-6.0.1-1
So what does this change do again?
Please remove the 3.7.12.1-1 packages. Also, run this from 'release' to
replace the setup.hint files with versions without 'prev', 'curr' and
'test' directives:
wget -e robots=off -X from-box --cut-dirs=1 -np -nH \
-A'setup.hint' -r http://etr-usa.com/cygwin/sqlite3/
I don't see any
On 8/8/2012 9:40 AM, Corinna Vinschen wrote:
On Aug 6 20:06, Warren Young wrote:
$ cd .../release
$ wget -e robots=off -X from-box --cut-dirs=1 -np -nH -A'*3.7.13-1*' \
-r http://etr-usa.com/cygwin/sqlite3/
That should populate the release/sqlite3 sub-tree correctly.
Not entirely
$ cd .../release
$ wget -e robots=off -X from-box --cut-dirs=1 -np -nH -A'*3.7.13-1*' \
-r http://etr-usa.com/cygwin/sqlite3/
That should populate the release/sqlite3 sub-tree correctly.
Please leave both 3.7.12-1 *and* 3.7.3-1 as prev, if that's possible. I
don't want 3.7.3-1 dropped
On 6/12/2012 6:48 AM, marco atzeri wrote:
still one.
@ nrss
That's owned by Jari Aalto, who appears to have gone MIA about three
months ago. That's the date of his last post to cygwin-l.
Also on this list, you'll find a couple of TTL-expired pings from Yaakov
to him regarding some of
When I took over maintainership of the Cygwin expat package, I asked
that this older ABI version of the library be kept for programs that
need it, but that was four years ago now. It's still there.
Assuming no one yells about it, I'd like to request that the Cygwin
package repo maintainers
Be in the release/expat directory:
wget -e robots=off --cut-dirs=2 -np -nH -A'*2.1.0-1*' -r \
http://etr-usa.com/cygwin/expat/
rmdir from-box
That should populate the repo hierarchy correctly.
(The from-box directory appears to be a gift from my web server.)
On 5/6/2012 3:26 PM, Yaakov (Cygwin/X) wrote:
On 2012-04-04 15:26, Warren Young wrote:
There's something about the way I have one of my development systems set
up that causes Cygport to chase a symlink loop infinitely in the Fixing
libtool modules: step of cygport install.
It apparently has
wget -e robots=off --cut-dirs=2 -np -nH -A'*3.7.12.1-1*' -r \
http://etr-usa.com/cygwin/sqlite3/
Please leave 3.7.3-1 as prev.
There's something about the way I have one of my development systems set
up that causes Cygport to chase a symlink loop infinitely in the Fixing
libtool modules: step of cygport install.
It apparently has something to do with the fact that the source for the
package in question lives under
New bogosity:
wget -e robots=off --cut-dirs=2 -np -nH -A'*4.1-1*' \
-r http://tangentsoft.net/cygwin/cd
On 3/29/2012 2:16 PM, Andrew Schulman wrote:
On Thu, Mar 29, 2012 at 11:26:59AM +0200, Corinna Vinschen wrote:
On Mar 29 09:51, Andy Koppe wrote:
Sorry to be so late in pointing this out, but Warren Young missed out
here. I think he deserves a gold star for redesigning the Cygwin logo.
I
On 11/23/2011 11:23 PM, Christopher Faylor wrote:
I wanted to extend my thanks to all of you package maintainers for the
giving of your time to the Cygwin project. You don't have to do what
you do but you do it anyway. It's pretty impressive.
There'd be nothing to package if there was no DLL
On 8/31/2011 3:42 AM, Corinna Vinschen wrote:
On Aug 30 13:51, Warren Young wrote:
On 8/30/2011 2:31 AM, Corinna Vinschen wrote:
So I'd still love to see a still with a beveled, less glossy C, if
that's ok with you...
did you have a chance to look into that?
Still plinking away
On 8/30/2011 2:31 AM, Corinna Vinschen wrote:
So I'd still love to see a still with a beveled, less glossy C, if
that's ok with you...
did you have a chance to look into that?
Still plinking away at it, an hour or so a night, off and on.
It requires completely rebuilding the 3D model.
On 8/20/2011 5:16 AM, Corinna Vinschen wrote:
Are GIFs always so low on colors?
Yes. GIF is limited to a 256-color palette. It's a hard technical
limit of the format, and was one of the driving forces behind the PNG
development effort.
Animation makes it worse because all the frames
On 8/19/2011 9:39 AM, Corinna Vinschen wrote:
On Aug 18 15:07, Warren Young wrote:
Cool! Here's how it looks like in the setup dialog:
http://cygwin.de/cygwin-splash.png
The faux motion blur should taper to match the logo's expansion. Going
straight down as it does now is optically
On 8/19/2011 4:23 PM, Warren Young wrote:
These links may be of some help:
http://msdn.microsoft.com/en-us/library/dd375468%28VS.85%29.aspx
http://stackoverflow.com/questions/530998/
Forgot one:
http://www.codeproject.com/KB/audio-video/DS_Player.aspx
On 8/17/2011 9:46 AM, Corinna Vinschen wrote:
On Aug 16 13:28, Warren Young wrote:
it would be fun to have a big logo
using the card box with a big 3D Cygwin C jumping out of the box on
the setup start screen.
Like this?
http://etr-usa.com/cygwin/logo/from-box/animation.webm
If you
On 8/16/2011 1:50 AM, Corinna Vinschen wrote:
On Aug 15 11:52, Warren Young wrote:
Now *that*, my friends, is an angry hippo.
Boy, is she pissed. I would be, too, if I had been confined to the box
that long.
The other way to look at it is that she is about to be unleashed upon
the world
On 8/16/2011 2:35 AM, Corinna Vinschen wrote:
On 15 August 2011 18:52, Warren Young wrote:
The problem for me is that the Cygwin C is only a sidenote now, and
that it lost its color.
On purpose. Few cardboard boxes have full-color logos on them.
It would be trivial to bring back the color
On 8/12/2011 3:12 AM, Corinna Vinschen wrote:
Turns out, 256 is too big for the splash screen. Looking for a nice
size, I found that 1064, the size of the rasterized original icon,
dived by 7 is 152, which looks like the ideal size for the dialog icon.
So I added a 152x152 icon to cygwin.ico,
On 8/14/2011 5:16 AM, Corinna Vinschen wrote:
On Aug 14 09:18, Andy Koppe wrote:
On 27 July 2011 18:30, Warren Young wrote:
- Do we need more sizes? I've seen reference to odd sizes like 64x64 and
96x96, but surely we can trust Vista+ to scale the 256x256 to these sizes
without needing hand
On 8/12/2011 12:59 AM, Corinna Vinschen wrote:
On Aug 11 15:06, Warren Young wrote:
I haven't forgotten about my attempt, by the way. It's just become
a bigger project than anticipated. I guess you're not waiting on
me, which is fine.
No, no, I'm curious.
I present to you now, my magnum
On 8/15/2011 9:44 AM, Charles Wilson wrote:
On 8/15/2011 10:33 AM, Warren Young wrote:
The hard edges in the original art are causing stair-stepping when doing
a direct downsample, though. (Look at the pointy bits.) By blurring
the high-res version and then downsampling by a non-integral
On 8/15/2011 11:58 AM, Chris Sutcliffe wrote:
On 15/08/2011 1:52 PM, Warren Young wrote:
I present to you now, my magnum opus:
http://etr-usa.com/cygwin/logo/boxed-hippo.ico
Now *that*, my friends, is an angry hippo.
When I try to grab the file I get an error stating it's malformed
On 8/15/2011 1:52 PM, Andy Koppe wrote:
On 15 August 2011 18:52, Warren Young wrote:
I present to you now, my magnum opus:
http://etr-usa.com/cygwin/logo/boxed-hippo.ico
Now *that*, my friends, is an angry hippo.
:)
That is rather impressive, and yep, that's not a happy hippo
On 8/11/2011 4:38 AM, Corinna Vinschen wrote:
New incarnation uploaded. Same URL. Is that better?
Yes, thanks.
I haven't forgotten about my attempt, by the way. It's just become a
bigger project than anticipated. I guess you're not waiting on me,
which is fine.
On 8/9/2011 1:25 AM, Corinna Vinschen wrote:
Erm... say that again? Here's where you're losing me. I don't even
know how to make the stroke thicker unless it would be a big, square
block.
Elaborating on steps I gave a few messages up the thread:
- enlarge the canvas to make room (Image
Updated upstream package.
wget -e robots=off --cut-dirs=2 -np -nH -A'*1.7.4-1*' -r \
http://etr-usa.com/cygwin/doxygen/
Leave current as prev.
On 8/10/2011 4:23 AM, Corinna Vinschen wrote:
On Aug 10 12:07, Corinna Vinschen wrote:
That looks excellent, IMHO. Can I just grab it for the official 32x32
terminal icon? There's no reason I should duplicate the work, right? ;)
Thanks. I jumped into this icon project to contribute, so,
On 8/6/2011 11:43 AM, Corinna Vinschen wrote:
Makes sense. If the outline needs to be any brighter, it would need to
be thickened before scaling down.
One way to do this without involving me:
- enlarge the canvas to make room
- right click stroke layer, alpha to selection
- select grow
-
On 8/7/2011 4:08 AM, Andy Koppe wrote:
the C with a thicker stroke, say twice as thick? (If you think I could
easily do that myself, just say so.)
So. :)
See my reply above.
On 8/6/2011 2:28 AM, Corinna Vinschen wrote:
Is that one ok as default Cygwin icon?
Works for me.
Did you figure out your problem seeing the 256 px icon? Was it just a
caching issue? If not, I wondered if reordering the icons in the
aggregate .ico file would help, so they're sorted
On 8/6/2011 12:27 PM, Corinna Vinschen wrote:
Now for the setup icon...
Here it is. The 32x32 icon is the most tricky one and needed some
convincing to look acceptable.
I'd make the C smaller in all of them, especially the 32x32. Please
point me to the box art. I want to try.
I also
On 8/8/2011 2:43 PM, Corinna Vinschen wrote:
If you have a way to create a C which
is not handdrawn *and* stands out, I would very much like to see it.
That's why I quoted Andy: increasing the stroke width can help. By
starting with a much thicker outer stroke, you end up with a brighter
On 8/8/2011 2:45 PM, Corinna Vinschen wrote:
On Aug 8 10:57, Warren Young wrote:
Did you figure out your problem seeing the 256 px icon?
I'm not sure what problem you mean. I can see the 256x256 icon just
fine.
I was half-remembering this message:
http://permalink.gmane.org
On 8/3/2011 11:49 PM, Andy Koppe wrote:
Warren's has the advantage of a 256 version and that it's more
tweakable assuming he provides the vector version it's presumably
based on.
Sorry, there is currently no vector version. Effects like bevels and
shadows are raster effects. However, based
On 8/4/2011 12:16 PM, Corinna Vinschen wrote:
On Aug 4 13:24, Charles Wilson wrote:
On 8/4/2011 10:29 AM, Corinna Vinschen wrote:
Nice, thank you. Do you know how to convert the green glow around
the C to grey, by any chance?
Not...exactly. I think you should be able to use the magic wand
On 8/5/2011 11:50 AM, Corinna Vinschen wrote:
You could also try moving the gamma slider, either alone, or in
combination with the above to keep the blacks where you want them.
I don't understand this. If I do that, the black C and especially the
highlights in the C are getting whiter and
On 8/5/2011 1:08 PM, Andy Koppe wrote:
I like this a lot. Thanks very much for responding so positively to my whinging.
Let me know if you need to see any other changes.
I think a large part of the problem is tl;dr, and the resultant talking
past each other. I know it's true for me.
I've
On 8/5/2011 2:04 PM, Andy Koppe wrote:
Which leaves the question how the icon with the 256x256 became so big.
I'd used a Cygwin build of 'icotool' from 'icoutils' for that,
icotool's --help is confusing. The magic incantation is:
$ icotool -c -o cygwin-term.ico -r cygwin-term.png
On 8/3/2011 2:37 PM, Andy Koppe wrote:
- The 256x256 version still has Warren's dark border around the
terminal. Not only is this spoiling the KDE Oxygen team's work,
There's a 50% transparent black (so, gray when composited over white)
border in the original KDE artwork. Are you saying you
Collecting all Corinna reply answers here:
On 7/28/2011 3:08 AM, Corinna Vinschen wrote:
It seems that black was a bad choice for the Cygwin C.
Is there a reason we cannot change it now? I don't see that Red Hat has
filed a US trademark on the logo. Even if they had, it's usually better
On 7/29/2011 9:21 AM, Buchbinder, Barry (NIH/NIAID) [E] wrote:
Warren Young sent the following at Friday, July 29, 2011 10:12 AM
http://etr-usa.com/cygwin/logo/glowing.ico
http://etr-usa.com/cygwin/logo/logo-glowing.ico
I've fixed it so the original URL is correct. (None
Couldn't resist doing another. I call this one The Matrix:
http://etr-usa.com/cygwin/logo/matrix.ico
On 7/27/2011 1:41 AM, Corinna Vinschen wrote:
You say you already have created such icon files before. Would you
have fun to create a new official cygwin.ico?
Here you go:
http://etr-usa.com/cygwin/mintty-icon/combined.ico
That file contains a 256 px 32 bpp (RGBA) Vista (PNG) icon
On 7/27/2011 2:04 PM, Andy Koppe wrote:
- The 16x16 has white dots in the corners.
That was a feature. But you no like it, I make go 'way.
- There are black edges around the icons. Those need to be transparent.
Why?
I purposely redrew the edges in the smaller icons for contrast and
On 7/26/2011 5:01 AM, Corinna Vinschen wrote:
This discussion reminds me of the new icon format in Vista, which
support icons of up to 256x256 bytes in PNG format.
Pixels, not bytes, unless you were thinking about 8 bpp paletted images.
I don't see -- in the almost nonexistent docs -- that
On 7/26/2011 2:17 AM, Corinna Vinschen wrote:
What about modernizing the Cygwin icon?
Check the other options in cygicons-0.dll. The one with the glowy green
wedge is okay.
Or, what about having a mintty
terminal icon with a small C in it? The only problem with this is, I'm
anything but
On 7/26/2011 7:45 AM, Charles Wilson wrote:
Fortunately, fatbuttlarry also provided a linux version (PNG, 237 x 256,
RGBA, 8 bit) that we could use to enhance the existing .ico
http://www.kde-look.org/content/show.php?content=36393
I've updated my
On 7/26/2011 1:36 PM, Andy Koppe wrote:
Regarding Warren's effort, the challenge is that it still needs to
look good at 16x16.
It's rather lazy to simply create the 16x16 by scaling down the 256x256.
It'd be better to take the existing 16x16 and package it with my
256x256, since the current
On 3/18/2011 12:06 AM, Christopher Faylor wrote:
On Thu, Mar 17, 2011 at 10:28:49PM -0500, Yaakov (Cygwin/X) wrote:
I wish to propose that Cygwin READMEs no longer be absolutely required
for Cygwin packages, for several reasons:
AFAIK, they never were absolutely required.
One could take
On 11/30/2010 12:00 PM, Corinna Vinschen wrote:
On Nov 4 15:07, Yaakov S wrote:
On Sun, 2010-10-03 at 02:04 -0500, Yaakov (Cygwin/X) wrote:
Cygwin's sqlite3 (3.6.21) is ten months old, and some current software
already needs more recent versions. Could you please update sqlite3 to
the latest
On 12/1/2010 6:58 AM, Warren Young wrote:
wget -e robots=off --cut-dirs=2 -np -nH -A'*3.6.21-3*' -r \
http://etr-usa.com/cygwin/sqlite3/
Grr...
wget -e robots=off --cut-dirs=2 -np -nH -A'*3.7.3-1*' -r \
http://etr-usa.com/cygwin/sqlite3/
On 6/2/2010 7:02 PM, Christopher Faylor wrote:
Does mintty currently work around any such problems?
I really don't understand the question in light of the observations that
there will be problems with some MS-DOS applications if we switch to
mintty because of cygwin's pty implementation.
On 6/3/2010 5:39 AM, Corinna Vinschen wrote:
Does anybody
have a problem with that? If so, would you take over maintainership
for pine?
Aren't all the cool kids using alpine now instead?
On 6/2/2010 3:01 PM, Christopher Faylor wrote:
It could be that there is an application
used by thousands that works well in the console window while failing
miserably under a tty/pty.
Does mintty currently work around any such problems?
If so, how hard is it to just keep finding them and
On 12/28/2009 1:26 PM, Christopher Faylor wrote:
On Mon, Dec 28, 2009 at 12:16:59PM -0800, Rob Walker wrote:
It's been almost a year and a half since I made a request to have
Cygwin's GNU make updated with the upstream patches for colons in
dependencies and VPATH directives:
Don't we get that
On 12/18/2009 3:23 AM, Corinna Vinschen wrote:
There are also older releases left,
1.5.1-1 and 1.5.5-1. The 1.5.1-1 release is from 2006. Shall we
remove it?
I'm not emotionally attached to those releases, but then, I don't use
doxygen on Cygwin. (I only use one of the packages I
The previous -2 release had a completely wrong source patch relative to
the original sources, which caused it to be all but useless. Thus,
everyone who got the -2 should upgrade.
Sorry wrong list. I'm on a *roll* this week...
This fixes some packaging errors in -1 and adds manpages to the package.
wget -e robots=off --cut-dirs=2 -np -nH -A'*1.6.1-2*' -r \
http://etr-usa.com/cygwin/doxygen/
Previous -1 should be removed.
This fixes a b0rked source patch -1 and -2, which should be removed.
wget -e robots=off --cut-dirs=2 -np -nH -A'*3.6.21-3*' -r \
http://etr-usa.com/cygwin/sqlite3/
Yes, I'm aware that I should be testing these packages better. No need
to tell me I am a doofus. I already know that.
On 12/15/2009 10:42 AM, David Rothenberger wrote:
Was this intentional?
No.
I don't know why, but my local .cygport file changed between 3.6.2-1 and
3.6.21-1, causing various files to be put into the wrong packages.
You'll also find that *.a went in the lib package, not devel.
I'm
This fixes packaging errors in -1, which should be removed.
wget -e robots=off --cut-dirs=2 -np -nH -A'*3.6.21-2*' -r \
http://etr-usa.com/cygwin/sqlite3/
On 12/14/2009 8:57 AM, Corinna Vinschen wrote:
On Dec 11 10:40, Warren Young wrote:
New upstream release:
Your setup.hint file still refers to libreadline6 while the latest
release is libreadline7.
Thanks, it's fixed now:
http://etr-usa.com/cygwin/sqlite3/setup.hint
New upstream release:
wget -e robots=off --cut-dirs=2 -np -nH -A'*3.6.21*' -r \
http://etr-usa.com/cygwin/sqlite3/
This is the first version packaged explicitly for 1.7. Previous 3.6.2
was copied over from 1.5 repo.
New upstream release:
wget -e robots=off --cut-dirs=2 -np -nH -A'*5.8-1*' -r \
http://etr-usa.com/cygwin/ctags/
setup.hint unchanged.
This is the first version packaged explicitly for 1.7. Previous 5.7 was
copied over from 1.5 repo.
New upstream release:
wget -e robots=off --cut-dirs=2 -np -nH -A'*1.6.1-1*' -r \
http://etr-usa.com/cygwin/doxygen/
setup.hint unchanged.
This is the first version packaged explicitly for 1.7. Previous 1.5.5
was copied over from 1.5 repo.
Christopher Faylor wrote:
Also, as far as I can tell, there is no remembering of anything going on
now. The buttons are off by default. Is that right or am I missing
something in the complicated setup code?
That's fine if setup.exe only directly creates the cmd.exe based shell
icons. It
Charles Wilson wrote:
I suggest adding a tag to setup.hint whose value is an icon title
#1. WAY too simplistic.
For some cases, sure. It suffices for many others, though, probably
even most others. If you want to add more tags to the design, fine, but
for v1.0, these other options
Christopher Faylor wrote:
No more RFU email - you get to upload stuff yourself.
Yay!
I hope you have an automated way to manage ssh keys. I find, with
Gna/Savannah, that I have to add or change a key every few months, due
to adding or replacing a build/test machine. I expect this to
Corinna Vinschen wrote:
What entanglement problem?
This one: http://www.cygwin.com/ml/cygwin/2009-01/msg00648.html
Well, that's not such a big issue, is it? As long as upgrading works
fine...
shrug It may be enough that the problem and the solution is now
documented on the list.
Maybe
Corinna Vinschen wrote:
Well, there's still the 1.5/1.7 entanglement problem, but that's not going
to be fixed, so we can't count that.
What entanglement problem?
This one: http://www.cygwin.com/ml/cygwin/2009-01/msg00648.html
Christopher Faylor wrote:
What problems are you trying to solve?
The one in the paragraph that you snipped.
I saw that you want a database, but I don't understand why. What does
this give you?
I don't doubt that there's a good answer. It's just that most of us
don't deal with upset, so
Charles Wilson wrote:
setup's understanding about
cygwin mount points, and setup's ability to faithfully recreate windows
ACL's and replace in-use files...)
Wouldn't cygwin1.dll give rpm.exe these abilities?
(2) cygwin rpm
+ much more complicated in-use file handling (because
Warren Young wrote:
Postponing postinstall scripts that depend on scheduled
file installation? Fuggetaboutit.
Can we postpone the script execution, too?
Another possibility occurs: instead of hiding all the MoveFileEx() stuff
inside setup.exe or rpm.exe, can cygwin1.dll be asked to do
Christopher Faylor wrote:
Would anyone mind if I changed the format of setup.hint to some
existing markup language?
What problems are you trying to solve?
I am not sure that the setup files require XML though.
I agree.
yaml
This seems closest to the current setup.hint format, and
A bit of history:
Back in May, Max Bowsher gave up maintainership of a bunch of packages.
I adopted a few of them, and released sqlite3-3.5.8-1. There was some
concern about the fact that my package didn't ship with a DLL version of
the library, only a static library. I got comments from
Corinna Vinschen wrote:
Any problem to prepare a script like Dr. Volker Zell does?
wget -O- http://etr-usa.com/cygwin/expat/slurp.sh |sh
Lapo Luchini wrote:
Dr. Volker Zell wrote:
usr/bin/lemon3.exe
Isn't this the parser-generator needed only for the build itself?
It's possible that some SQLite users have come to rely on it, assuming
it will be available. It's not entirely an internal use only tool; it
has its own web
David Ziants wrote:
Are all the mirrors equal?
They're supposed to be. If you can rediscover the problem mirror, you
should report it here.
Dr. Volker Zell wrote:
I would also recommend to build outside of the source tree.
I didn't know it was possible with non-autoconf build systems. Thank
you for cluing me in about:
lndirs
this. :)
-MAN1DIR = man/man1
+MAN1DIR = share/man/man1
Yes, too bad there isn't a
Corinna Vinschen wrote:
What are the names of the subdirs? Which files should be in which dir?
Can you please rearrange this to a working expat directory tree which
can be uploaded with a single wget?
Sorry, I didn't realize you were leaving such decisions up to newbie
maintainers like me.
Dr. Volker Zell wrote:
When building and packaging with your .cygport file I do not get shared
libs.
It may not be possible. It's set to try to build shared libraries, but
you get this during the build:
libtool: link: warning: undefined symbols not allowed in i686-pc-cygwin
shared
New maintainer, new upstream version, new packaging system. The
problems that came up in the ITA thread of last week have been fixed.
files:
http://etr-usa.com/cygwin/doxygen/setup.hint
http://etr-usa.com/cygwin/doxygen/doxygen-1.5.5-1.tar.bz2
New maintainer, new upstream version, new packaging system. The
problems that came up in the ITA thread of last week have been fixed.
Note that the following set of files includes a legacy libexpat0 package
and a new hint file for the old version of expat. This introduces
libexpat1, which
New maintainer, new upstream version, new packaging system. The
problems that came up in the ITA thread of last week have been fixed.
executables:
http://etr-usa.com/cygwin/sqlite3/setup.hint
http://etr-usa.com/cygwin/sqlite3/sqlite3-3.5.8-1.tar.bz2
shared library:
Charles Wilson wrote:
How is cygport supposed to
create, ex nihilo, your custom README and custom .hint files,
I don't expect it to. I keep versions of these files in the same
directory as the cygport file. cygport could be told about these files,
and copy them into the proper location
Yaakov (Cygwin Ports) wrote:
It's been in Ports for over a year...
Yes, but your version builds a whole bunch of bindings and such that you
can't do using only packages in the official Cygwin distro. When I said
I couldn't get graphviz to build, it's because I was still in the
process of
Dr. Volker Zell wrote:
Builds fine from source, but the cygwin specific patch has 0 bytes. So
there is no README and the .hint files are missing
Yeah, I've been meaning to ask about that...
Is there a way I can get Cygport to generate this patch for me? It
seems like it should be able to
Yaakov (Cygwin Ports) wrote:
| Is there a way I can get Cygport to generate this patch for me?
You need to put these files into foo-ver-rel/CYGWIN-PATCHES/.
I actually stumbled across that earlier, but I convinced myself it
couldn't be the right way to do it.
foo-ver-rel doesn't exist
Christopher Faylor wrote:
I'd like to get a list of things to check for.
- Missing README and setup.hint in the -src.tar.bz2. (No cygwin.patch)
Yaakov (Cygwin Ports) wrote:
For those that may be interested in adoption, there are updated versions
of some of these now in Ports:
Okay, thanks for the leg up. I'm guessing you'll keep maintaining these
packages? I started my versions from yours, but had to remove several
features
Taking over maintainership of this package from Max Bowsher. Ported
build from g-b-s to cygport and updated from 1.5.1 to 1.5.5, so I'd like
at least one GTG before I post the RFU message.
http://etr-usa.com/cygwin/doxygen/setup.hint
http://etr-usa.com/cygwin/doxygen/doxygen-1.5.5-1.tar.bz2
101 - 200 of 245 matches
Mail list logo
