On 13/11/2017 19:59, Thomas Wolff wrote:
Am 25.10.2017 um 21:42 schrieb Jon Turney:
I propose that calm will stop accepting uploads containing setup.hint
some time shortly after 2017-11-18.
So, firstly this plan has been superseded...
This is approximately one year after the cygport release
Thomas Wolff writes:
> If calm can simply "rename setup.hint to pvr.hint", what's the purpose
> of all this?
One of the purposes is that dependencies can and do change over time and
eventually we will want to have separate dependencies for each released
package like everybody else
Am 25.10.2017 um 21:42 schrieb Jon Turney:
I propose that calm will stop accepting uploads containing setup.hint
some time shortly after 2017-11-18.
This is approximately one year after the cygport release [1] which,
stopped generating these files, so if you're using cygport >= 0.2
; I propose that calm will stop accepting uploads containing setup.hint
> > > > > some
> > > > > time shortly after 2017-11-18.
>
> Better plan: when uploaded, calm will rename a setup.hint file to pvr.hint.
>
> (If the appropriate pvr cannot be determin
On 25/10/2017 22:18, Corinna Vinschen wrote:
On Oct 25 21:46, Jon Turney wrote:
On 25/10/2017 21:23, Corinna Vinschen wrote:
On Oct 25 20:42, Jon Turney wrote:
I propose that calm will stop accepting uploads containing setup.hint some
time shortly after 2017-11-18.
Better plan: when
On Oct 25 21:46, Jon Turney wrote:
> On 25/10/2017 21:23, Corinna Vinschen wrote:
> > On Oct 25 20:42, Jon Turney wrote:
> > >
> > > I propose that calm will stop accepting uploads containing setup.hint some
> > > time shortly after 2017-11-18.
> > >
On Oct 25 20:42, Jon Turney wrote:
>
> I propose that calm will stop accepting uploads containing setup.hint some
> time shortly after 2017-11-18.
>
> This is approximately one year after the cygport release [1] which, stopped
> generating these files, so if you're using
I propose that calm will stop accepting uploads containing setup.hint
some time shortly after 2017-11-18.
This is approximately one year after the cygport release [1] which,
stopped generating these files, so if you're using cygport >= 0.23.0, no
action is needed.
Warnings that you n
in the last 3 months only cygwin, mintty and gcc packages
where using setup.hint
And probably they are all cross-compiled ..
I deployed a small update to calm today:
Unneeded setup.hint files will now be removed from the release area.
Additionally, a warning telling you to upgrade cygport will now
packages
where using setup.hint
And probably they are all cross-compiled ..
Regards
Marco
On 05/04/2017 21:55, Marco Atzeri wrote:
On 04/04/2017 19:38, Jon Turney wrote:
On 04/04/2017 14:28, Marco Atzeri wrote:
Not sure if "calm" is excluding them, but I noticed for some
packages we have now an excess of "setup.hint" as all existing
revision have their own
On 04/04/2017 19:38, Jon Turney wrote:
On 04/04/2017 14:28, Marco Atzeri wrote:
Not sure if "calm" is excluding them, but I noticed for some
packages we have now an excess of "setup.hint" as all existing
revision have their own package-revison.hint
These old setup.hint fi
On 04/04/2017 14:28, Marco Atzeri wrote:
Not sure if "calm" is excluding them, but I noticed for some
packages we have now an excess of "setup.hint" as all existing
revision have their own package-revison.hint
These old setup.hint files should be benign, unless they are
Hi,
Not sure if "calm" is excluding them, but I noticed for same
packages we have now an excess of "setup.hint" as all existing
revision have their own package-revison.hint
libopenssl100/ 26-Jan-2017 20:44
Hi Jon,
following our previous discussion about setup.hint transition.
As Yaakov asked to rebuild mutt, that I just rebuild last week
I have the problem of what to do of the current "setup.hint",
as "calm" did not allow to remove last time.
Current situation
mutt-1.7.0-1-src
On 2016-09-01 12:12, Jon Turney wrote:
On 30/08/2016 13:24, Jon Turney wrote:
For a source-only package, rather than just a skip: key, write category:,
requires:, ldesc: and sdesc: keys as well.
This had a rather unfortunate bug which made it always generate a
source-only package hint (i.e.
rather than setup.hint
For a source-only package, rather than just a skip: key, write category:,
requires:, ldesc: and sdesc: keys as well.
v2:
Only generate a source-only package hint with skip: when nothing else has
generated the package hint, rather than always
Signed-off-by: Jon Turney &l
r more setup package categories. This will be
-# used as the category: field of auto-generated setup.hint files.
+# used as the category: field of auto-generated .hint files.
# NOTE
# A list of official categories is available on the
# |html http://cygwin.com/setup.html#setup.hint;>Cygwi
On 17/02/2016 14:23, Jon Turney wrote:
On 09/02/2016 17:10, Corinna Vinschen wrote:
On Feb 9 13:18, Jon Turney wrote:
* 'sdesc' text is mangled in setup.ini (but not the HTML package
list)
In particular, it is forced to start with a capital letter (which
is incorrect when the sdesc starts
regex. IN any case,
that's not a problem we need to solve now.
>> So the proposal is to remove skip or make it mandatory for source-only
>> packages?
>
> I'm not sure. I think I tend towards removing it, since it doesn't
> add any information.
OK.
> But currently cygport
On Feb 17 14:23, Jon Turney wrote:
> On 09/02/2016 17:10, Corinna Vinschen wrote:
> >IMHO we don't need "skip". A source-only package should be
> >automatically skipped anyway. What other reason do we need to ignore
> >a package?
>
> Yes, this is why I ask the question.
>
> I don't see what
On 09/02/2016 17:10, Corinna Vinschen wrote:
On Feb 9 13:18, Jon Turney wrote:
* 'sdesc' text is mangled in setup.ini (but not the HTML package list)
In particular, it is forced to start with a capital letter (which is
incorrect when the sdesc starts with a command name which is properly
Jon Turney writes:
> I think currently UTF-8 displays correctly in the HTML package pages,
> but neither encoding displays correctly in setup.
>
> I'd suggest that we specify UTF-8 and eventually fix setup to handle that.
UTF-8 these days, please.
> I'd suggest this mangling is removed, and
While I've been looking at replacement/improvement for the current upset
script, I've come across some minor issues related to
under-specification or under-documentation of setup.hint:
* The encoding of setup.hint is unspecified.
Historically both ISO-8859-1 and UTF-8 have been used. (e.g
On Feb 9 13:18, Jon Turney wrote:
>
> While I've been looking at replacement/improvement for the current upset
> script, I've come across some minor issues related to under-specification or
> under-documentation of setup.hint:
>
> * The encoding of setup.hint is unspecified.
There are a number of packages still requiring obsoleted Perl packages
that I want to delete now, so these setup.hint files need to be fixed.
Here is what I've found so far with a proposed replacement in
parenthesis.
perl_vendor (only on 32bit since it never existed on 64bit):
===
Yaakov
Corinna Vinschen writes:
>> Remark: SWI Prolog doesn't compile from the source package.
>
> It did when I created it.
Well, certainly. :-)
> Yes, it's spurious. I removed the perl_vendor from setup.hint for now.
> I don't intend to repackage SWI-Prolog for a while.
Thanks
On Dec 17 19:27, Achim Gratz wrote:
>
> There are a number of packages still requiring obsoleted Perl packages
> that I want to delete now, so these setup.hint files need to be fixed.
> Here is what I've found so far with a proposed replacement in
> parenthesis.
>
> perl_
Jon Turney writes:
> I fixed on cygwin.com various spelling errors or typos in setup.hint:
[…]
> AG: perl-TimeDate: formating -> formatting
That typo in the description is from upstream, it gets generated from
the META information on CPAN. :-)
http://api.metacpan.org/v0/release/Time
I fixed on cygwin.com various spelling errors or typos in setup.hint:
Please update your local copy
JA: apngdis: invividual -> individual
YS: artikulate : pronounciation -> pronunciation
YS: autoconf2.1: creattes -> creates
JY: binutils: assember -> assembler
MA: catdoc
On Fri, 2015-10-23 at 14:48 +0100, Jon Turney wrote:
> I fixed on cygwin.com various spelling errors or typos in setup.hint:
>
> Please update your local copy
Done, thanks!
--
Yaakov
On 8/25/2015 7:37 AM, Andrew Schulman wrote:
I have a package in test, that I want to promote to current. If I just upload
the revised setup.hint and !ready, is that enough?
Yes.
Ken
I have a package in test, that I want to promote to current. If I just upload
the revised setup.hint and !ready, is that enough? Or do I need to re-upload
the package .tar.xz files too, and/or bump the version number?
quite so
much. OTOH setting PREV, CURR and TEST feels a little more natural to me with
the current 3-version setup.
Either way would be fine with me, as long as I have a way of automatically
setting the versions in the cygport file, instead of having to manually edit
setup.hint after
Andrew Schulman writes:
I have a package (socat) where I need to set the curr: and test: fields in
setup.hint. I got tired of adding them to the autogenerated setup.hint files
after every build, so I wrote a patch for cygport to support specifying them
in
the cygport file. For example
a little more natural to me with
the current 3-version setup.
Either way would be fine with me, as long as I have a way of automatically
setting the versions in the cygport file, instead of having to manually edit
setup.hint after the build.
Andrew
I have a package (socat) where I need to set the curr: and test: fields in
setup.hint. I got tired of adding them to the autogenerated setup.hint files
after every build, so I wrote a patch for cygport to support specifying them in
the cygport file. For example, setting
CURR=1.7.3.0-2
TEST
On 25/09/2014 22:05, David Stacey wrote:
I am trying to package tinyxml2, to be used by cppcheck. I have split
the package into a library package called 'libtinyxml2-2', and a devel
package 'libtinyxml2-devel'. However, when I run cygport to generate the
packages, the setup.hint file
the
packages, the setup.hint file for the devel package claims that it is
dependent on 'libtinyxml2' (note the missing '-2' at the end).
the package should be called libtinyxml2_2
That fixed it - thank you for your help.
Cheers,
Dave.
Hi,
In the web page that describes the new upload method there is no mention
of setup.hint. Is it not required to upload setup.hint? How are
requires, categories, and descriptions defined?
--
Erwin Waterlander
http://waterlan.home.xs4all.nl/
Il 1/5/2014 9:27 PM, waterlan ha scritto:
Hi,
In the web page that describes the new upload method there is no mention
of setup.hint. Is it not required to upload setup.hint? How are
requires, categories, and descriptions defined?
setup.hint's are need, of course as they are the base
marco atzeri schreef op 2014-01-05 21:48:
Il 1/5/2014 9:27 PM, waterlan ha scritto:
Hi,
In the web page that describes the new upload method there is no
mention
of setup.hint. Is it not required to upload setup.hint? How are
requires, categories, and descriptions defined?
setup.hint's
Il 1/5/2014 9:52 PM, waterlan ha scritto:
marco atzeri schreef op 2014-01-05 21:48:
Il 1/5/2014 9:27 PM, waterlan ha scritto:
Hi,
In the web page that describes the new upload method there is no mention
of setup.hint. Is it not required to upload setup.hint? How are
requires, categories
The pcre directory has a setup.hint with just skip: as the only entry.
This would indicate a source-only package, however pcre does have a
package with documentation and binaries that can't be installed due to
this.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk
On 2013-10-07 13:03, Achim Gratz wrote:
The pcre directory has a setup.hint with just skip: as the only entry.
This would indicate a source-only package, however pcre does have a
package with documentation and binaries that can't be installed due to
this.
Fixed, thanks for noticing.
Yaakov
Some of the *.exe files I compile under 64 report dependencies like this:
...
C:\tmp\cygwin\root\bin\cygz.dll
C:\tmp\cygwin\root\bin\cygstdc++-6.dll
C:\tmp\cygwin\root\bin\cyggcc_s-seh-1.dll
The first two are obvious, but what is the last one? What requires:
should I put in setup.hint
Jari Aalto writes:
C:\tmp\cygwin\root\bin\cyggcc_s-seh-1.dll
The first two are obvious, but what is the last one? What requires:
should I put in setup.hint to satisfy it?
Asking the orcale at:
http://cygwin.com/cgi-bin2/package-grep.cgi?grep=cyggcc_s-seh-1.dllarch=x86_64
gives the answer
I noticed on the 64 bit tree that the following files
base-cygwin-3.2-1.tar.bz2
gzip-1.4-1.tar.bz2
winsup-20130314-svn-1.tar.bz2
are missing the relevant setup.hint
Regards
Marco
On Mar 22 11:30, marco atzeri wrote:
I noticed on the 64 bit tree that the following files
base-cygwin-3.2-1.tar.bz2
gzip-1.4-1.tar.bz2
winsup-20130314-svn-1.tar.bz2
are missing the relevant setup.hint
Thanks for the hint. I added these files.
Corinna
--
Corinna Vinschen
On Oct 23 07:38, Jari Aalto wrote:
Please upload this apngtools metapackage for users that want to get all
in download.
wget --recursive --no-host-directories --cut-dirs=3 \
http://cante.net/~jaalto/tmp/cygwin/apngtools/setup.hint \
I would love to, but it looks like there's
On 2012-10-23 09:44, Corinna Vinschen wrote:
| I would love to, but it looks like there's something amiss here... ;)
Extra backslash removed from URL and commas from setup.hint::required field:
wget --recursive --no-host-directories --cut-dirs=3 \
http://cante.net/~jaalto/tmp/cygwin
On Oct 23 16:24, Jari Aalto wrote:
On 2012-10-23 09:44, Corinna Vinschen wrote:
| I would love to, but it looks like there's something amiss here... ;)
Extra backslash removed from URL and commas from setup.hint::required field:
wget --recursive --no-host-directories --cut-dirs=3
2012-10-23 16:43 Corinna Vinschen
| I think we need empty apngtools bin and src packages as well. Just
| a setup.hint file seems a bit on the lean side.
Ok. Created an empty package for the effect of setup.hint only.
wget --recursive --no-host-directories --cut-dirs=3 \
http://cante.net
Please upload this apngtools metapackage for users that want to get all
in download.
wget --recursive --no-host-directories --cut-dirs=3 \
http://cante.net/~jaalto/tmp/cygwin/apngtools/setup.hint \
Jari
[ setup.hint ]
sdesc: Animated PNG image (APNG) tools
ldesc: Collection
apng tools package ?
The compilations can be handled through metapackages that depend on
individual packages[*]. See Ubuntu etc.
After RFU'ing these, we can upload:
wget --recursive --no-host-directories --cut-dirs=3 \
http://cante.net/~jaalto/tmp/cygwin/apngtools/setup.hint \
Jari
On 7/20/2012 5:20 PM, Ken Brown wrote:
On 7/20/2012 3:27 PM, Yaakov (Cygwin/X) wrote:
On 2012-07-20 11:19, Ken Brown wrote:
1. The setup.hint generated for emacs (but not emacs-X11) erroneously
listed perl and python in the requires. I'm attaching my .cygport
file and the associated patches
Ken Brown writes:
How about something like [PKG_]REQUIRE_EXCLUDES for packages that we
don't want to require?
Any further thoughts about this?
+1
Since I have made a snapshot package, cygport picks up that package as a
dependency. I've patched pkg.cygpart to filter these out (grep -Ev
On 2012-07-19 00:22, Yaakov (Cygwin/X) wrote:
On 2012-07-18 06:53, Ken Brown wrote:
When I build a package using cygport, I sometimes forget to run
cygport's dep command to make sure my setup.hint is up to date. I
think it would be useful for cygport to do this as part of its packaging
step
On 7/20/2012 8:35 AM, Yaakov (Cygwin/X) wrote:
On 2012-07-19 00:22, Yaakov (Cygwin/X) wrote:
On 2012-07-18 06:53, Ken Brown wrote:
When I build a package using cygport, I sometimes forget to run
cygport's dep command to make sure my setup.hint is up to date. I
think it would be useful
, that was fast. Thanks!
I was already working on the setup.hint generation earlier this week; I
just had to add in the dependency generation, the framework for which
was there already in __list_deps (although I added to it). That being
said, it came together even faster than I had anticipated.
I
to remove your .hint files from $C.
Wow, that was fast. Thanks!
I was already working on the setup.hint generation earlier this week; I
just had to add in the dependency generation, the framework for which
was there already in __list_deps (although I added to it). That being
said, it came
When I build a package using cygport, I sometimes forget to run
cygport's dep command to make sure my setup.hint is up to date. I
think it would be useful for cygport to do this as part of its packaging
step. It could print out a list of dependencies or, better, print a
warning
On 2012-07-18 06:53, Ken Brown wrote:
When I build a package using cygport, I sometimes forget to run
cygport's dep command to make sure my setup.hint is up to date. I
think it would be useful for cygport to do this as part of its packaging
step. It could print out a list of dependencies
upset: Error. Parsing failed. - release/octave/setup.hint(9): can't use [] here
I've changed octave's setup.hints to add prev:, curr:, test:
lines, removing the incorrect setup.ini format.
On 9/21/2011 4:02 PM, Christopher Faylor wrote:
upset: Error. Parsing failed. - release/octave/setup.hint(9): can't use [] here
I've changed octave's setup.hints to add prev:, curr:, test:
lines, removing the incorrect setup.ini format.
I wrongly copied the setup.ini structure instead
I'd like to promote the test releases (23.3-2) to current. I think the
following setup.hint files should do the job.
wget -x -nH --cut-dirs=2 \
http://www.math.cornell.edu/~kbrown/cygwin/emacs/setup.hint \
http://www.math.cornell.edu/~kbrown/cygwin/emacs/emacs-X11/setup.hint \
http
On Tue, Apr 19, 2011 at 04:56:05PM -0400, Ken Brown wrote:
I'd like to promote the test releases (23.3-2) to current. I think the
following setup.hint files should do the job.
wget -x -nH --cut-dirs=2 \
http://www.math.cornell.edu/~kbrown/cygwin/emacs/setup.hint \
http
On 22/03/2011 21:45, Christopher Faylor wrote:
On Tue, Mar 22, 2011 at 09:16:58PM +, Dave Korn wrote:
Also, I can't post the release announcement, because the spam filter
complains that I have things that look like raw email addresses in the
body. Mailing the global allow address didn't
Hi folks,
I just uploaded gcc4-4.3.4-4, and realised the setup.hint requires: lines
don't reflect the extra dependencies that 4.5.0-1 requires. There will be a
brief window while I fix this when anyone installing 4.5.0 might not get all
the libs like MPC GMP etc. that they need.
Also
On 22/03/2011 21:16, Dave Korn wrote:
I just uploaded gcc4-4.3.4-4, and realised the setup.hint requires: lines
don't reflect the extra dependencies that 4.5.0-1 requires. There will be a
brief window while I fix this when anyone installing 4.5.0 might not get all
the libs like MPC GMP etc
On 3/22/2011 5:19 PM, Dave Korn wrote:
Guess I forgot to actually ask: Do we prefer the situation where all users
of curr: packages get a few extra libs that they don't need, or would we
prefer not to make them download extra libs and rely on users of test:
packages to manually download
On 22/03/2011 21:44, Charles Wilson wrote:
On 3/22/2011 5:19 PM, Dave Korn wrote:
Guess I forgot to actually ask: Do we prefer the situation where all users
of curr: packages get a few extra libs that they don't need, or would we
prefer not to make them download extra libs and rely on users
On Tue, Mar 22, 2011 at 09:16:58PM +, Dave Korn wrote:
Also, I can't post the release announcement, because the spam filter
complains that I have things that look like raw email addresses in the
body. Mailing the global allow address didn't help - can anyone get it
through manually?
Looking
On Jun 24 18:23, Charles Wilson wrote:
On 6/24/2010 5:02 PM, Yaakov (Cygwin/X) wrote:
Do you know yet what the actual DLL names are going to be? libkio
dlopen()s these instead of linking against them, so I want to fix these
for my next KDE release.
[...]
(obviously those last two would
On Jun 24 23:21, Matthias Andree wrote:
Corinna Vinschen wrote on 2010-06-24:
On Jun 24 20:13, Matthias Andree wrote:
Corinna Vinschen wrote on 2010-06-24:
I have no idea about this stuff. I'm maintaining openssl primarily
since it's required for openssh. If there's anything which isn't
this in the
setup.hint files on cygwin.com, but, please do this in your local copy
of your setup.hint files as well.
As soon as I upgraded to openssl-1.0.0a-1, make sure that you keep your
package dependencies in shape when building a new package. That means
to change from libopenssl098
So, what we have to do is to convert *ALL* existing package dependencies
from openssl to libopenssl098. I'm going to do this in the
setup.hint files on cygwin.com, but, please do this in your local copy
of your setup.hint files as well.
Done.
Corinna Vinschen wrote on 2010-06-24:
Hi guys,
according to the discussion starting here
http://cygwin.com/ml/cygwin-apps/2010-06/msg00101.html
the layout of the openssl package has changed so that the runtime
libraries are now in the libopenssl098 package, rather than in the
openssl base
On Jun 24 15:55, Matthias Andree wrote:
Corinna Vinschen wrote on 2010-06-24:
Hi guys,
according to the discussion starting here
http://cygwin.com/ml/cygwin-apps/2010-06/msg00101.html
the layout of the openssl package has changed so that the runtime
libraries are now in the libopenssl098
Corinna Vinschen wrote on 2010-06-24:
On Jun 24 15:55, Matthias Andree wrote:
Corinna Vinschen wrote on 2010-06-24:
Hi guys,
according to the discussion starting here
http://cygwin.com/ml/cygwin-apps/2010-06/msg00101.html
the layout of the openssl package has changed so that the runtime
On Jun 24 20:13, Matthias Andree wrote:
Corinna Vinschen wrote on 2010-06-24:
I have no idea about this stuff. I'm maintaining openssl primarily
since it's required for openssh. If there's anything which isn't
fixed upstream, it won't be fixed for Cygwin. The Cygwin 1.0.0a-1
package is
On Thu, 2010-06-24 at 21:41 +0200, Corinna Vinschen wrote:
Openssl does not come with any certificate and there's no certificate
package in Cygwin either. AFAICS it would be sufficient to move to
another ssl directory like, say, /usr/share/ssl instead of /usr/ssl.
The user can copy and rehash
On Jun 24 14:55, Yaakov S wrote:
On Thu, 2010-06-24 at 21:41 +0200, Corinna Vinschen wrote:
Openssl does not come with any certificate and there's no certificate
package in Cygwin either. AFAICS it would be sufficient to move to
another ssl directory like, say, /usr/share/ssl instead of
On Thu, 2010-06-24 at 22:25 +0200, Corinna Vinschen wrote:
Openssl's configuration only allows two location options, --prefix,
which is set to /usr, and --openssldir, which is set to /usr/ssl
by default. So, if we change --openssldir to /usr/share/ssl, all
files will move there, including the
On Thu, 2010-06-24 at 11:36 +0200, Corinna Vinschen wrote:
So, what we have to do is to convert *ALL* existing package dependencies
from openssl to libopenssl098. I'm going to do this in the
setup.hint files on cygwin.com, but, please do this in your local copy
of your setup.hint files
Corinna Vinschen wrote on 2010-06-24:
On Jun 24 20:13, Matthias Andree wrote:
Corinna Vinschen wrote on 2010-06-24:
I have no idea about this stuff. I'm maintaining openssl primarily
since it's required for openssh. If there's anything which isn't
fixed upstream, it won't be fixed for
On 6/24/2010 5:02 PM, Yaakov (Cygwin/X) wrote:
Do you know yet what the actual DLL names are going to be? libkio
dlopen()s these instead of linking against them, so I want to fix these
for my next KDE release.
When I built it for (a cygwin fork that shall not be named), they were:
On 25/06/2010 7:02 AM, Yaakov (Cygwin/X) wrote:
On Thu, 2010-06-24 at 11:36 +0200, Corinna Vinschen wrote:
So, what we have to do is to convert *ALL* existing package dependencies
from openssl to libopenssl098. I'm going to do this in the
setup.hint files on cygwin.com, but, please do
Please re-upload the setup.hint for orpie. I've relaxed the dependency on
lapack to just liblapack0, which will avoid lapack's repeated
reinstallation problem in setup. Thanks, Andrew.
wget http://home.comcast.net/~andrex2/cygwin/orpie/setup.hint
On Jan 21 07:59, Andrew Schulman wrote:
Please re-upload the setup.hint for orpie. I've relaxed the dependency on
lapack to just liblapack0, which will avoid lapack's repeated
reinstallation problem in setup. Thanks, Andrew.
wget http://home.comcast.net/~andrex2/cygwin/orpie/setup.hint
2009/12/27 Christopher Faylor:
- Forwarded message from Ivanyi Peter -
I just fixed the wrong setup.hint yesterday,
so it could be that you got a broken setup.hint with no dependencies at
all.
You need those packages:
libgcc1 libgdbm4 libdb4.5 crypt libexpat1 libbz2_1
- Forwarded message from Ivanyi Peter -
I just fixed the wrong setup.hint yesterday,
so it could be that you got a broken setup.hint with no dependencies at
all.
You need those packages:
libgcc1 libgdbm4 libdb4.5 crypt libexpat1 libbz2_1
shows that cygssp-0.dll
I've adjusted the setup.hint for a few packages to more accurately reflect the
fonts they require, notes on which I've been collecting at [1]
xedit: remove dependency on dpi100 versions of several font packages
xman: change to depend on dpi75 not dpi100 versions of font-adobe and font-bh
gvim
I'm promoting the current test versions of screen to current. Please
upload the revised setup.hints (below) to make the change. All I've done
is to remove the test: and curr: lines from each setup.hint. Thanks,
Andrew.
# 1.5
wget http://home.comcast.net/~andrex2/cygwin/1.5/screen/setup.hint
On 30/09/2009 10:56, Andrew Schulman wrote:
I'm promoting the current test versions of screen to current. Please
upload the revised setup.hints (below) to make the change. All I've done
is to remove the test: and curr: lines from each setup.hint. Thanks,
Done.
Yaakov
Please upload revised setup.hint files, below, for lftp for Cygwin 1.5 and
1.7. The previous setup.hints were missing some package dependencies.
For people whose lftp installations are broken because they didn't get all
of the necessary dependencies when they installed lftp the first time
On Tue, Jul 21, 2009 at 04:14:47PM -0400, Andrew Schulman wrote:
Please upload revised setup.hint files, below, for lftp for Cygwin 1.5 and
1.7. The previous setup.hints were missing some package dependencies.
For people whose lftp installations are broken because they didn't get all
On Tue, Jul 21, 2009 at 04:39:52PM -0400, Christopher Faylor wrote:
On Tue, Jul 21, 2009 at 04:14:47PM -0400, Andrew Schulman wrote:
Please upload revised setup.hint files, below, for lftp for Cygwin 1.5 and
1.7. The previous setup.hints were missing some package dependencies.
For people whose
# 1.5
wget http://home.comcast.net/~andrex2/cygwin/1.5/lftp/setup.hint
Btw, this has a dependency on libreadline7. I changed it to libreadline6
since that is the newest package available for 1.5.
Right, thanks.
Following [1] and other previous difficulties, I've added 'font-misc-misc
font-adobe-dpi75 font-alias' to the 'requires:' for xterm
This should be the minimal set of additions that xterm now starts up free of
warnings
[1] http://cygwin.com/ml/cygwin-xfree/2009-06/msg00067.html
1 - 100 of 294 matches
Mail list logo
