On Saturday, May 11, 2002, at 10:15 AM, Jeremy Higgs wrote:
dependency on qt-2.3.1-1 (I have tried ( 3.0.0-1), but that doesn't
install the qt-2.3.1-1 package.)...
Have you tried (= 2.3.1-1)
HTH
Matt
___
Have big pipes?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
### Matt Stephenson [Sat, May 11, 2002 at 05:58:39PM +1000]
The current qt package in stable
Oh, okay -- the X11 based one. I thought you were talking about the
Quartz-based native Qt/Mac... Forgot that that one is non-free :-(
- --
Karin Kosina
I am still having problems with this package. Now it doesn't want to be
installed nor to be removed (actually, after jumping through a couple of
hoops that I forgot, but at least involving sudo touch
/sw/var/lib/emacsen-common/installed-flavors, I got it reinstalled and
then removed. Won't touch
At 23:49 Uhr -0700 10.05.2002, Ben Hines wrote:
Just checked in puf, a parallel URL fetching utility. We might
consider it as a downloader for fink.
To solve the what if one fails? problem we could check to see if
the files exist in src after puf exits.
That's only useful if we first
At 11:51 AM +0200 5/11/02, Max Horn wrote:
At 23:49 Uhr -0700 10.05.2002, Ben Hines wrote:
Just checked in puf, a parallel URL fetching utility. We might
consider it as a downloader for fink.
To solve the what if one fails? problem we could check to see if
the files exist in src after puf
Of course i suppose we'd have to update every package
Not necessarily. If the Source-MD5 field is present, fink should check
against it; if not, fink would let the download through. It then would
be up to the maintainers of packages to add this if they wanted.
-- Dave
Which is the right package for emacs with carbon support - alpha or
carbon???
Thank you!
Thomas
___
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL
I am moving this to devel, because this problem is of a more principal nature.
Martin Costabel wrote:
I have a different problem with qt3: It builds completely, but does not
install, due to
qt3-shlibs conflicts with qt-shlibs
qt-shlibs (version 3.0.3-3) is installed.
dpkg: error
OK, still replying to myself. I think I understand this now, but I would
say this whole business is not a brilliant demonstration of the
usefulness of the shlibs-splitoff story. In this special case, it was
less than useful.
Martin Costabel wrote:
So it seems that while the qt-shlibs package
On Saturday, May 11, 2002, at 06:39 AM, David R. Morrison wrote:
I'll put qt2 next on my list of packages to make a splitoff version of.
(We need one so that qt2 and qt3 can coexist.)
I'm already working on one. It finished building last night, I just
need to make sure I've got things all
On Saturday, May 11, 2002, at 08:47 AM, Martin Costabel wrote:
OK, still replying to myself. I think I understand this now, but I would
say this whole business is not a brilliant demonstration of the
usefulness of the shlibs-splitoff story. In this special case, it was
less than useful.
At 4:13 Uhr -0700 11.05.2002, Ben Hines wrote:
At 7:07 AM -0400 5/11/02, David R. Morrison wrote:
Of course i suppose we'd have to update every package
Not necessarily. If the Source-MD5 field is present, fink should check
against it; if not, fink would let the download through. It then
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have been getting this error, but I cannot figure out why.
making `install' in directory /sw/src/xgks-2.6-1/xgks-2.6/src/port/fortc
cp fortc /sw/bin/fortc
make[3]: Nothing to be done for `installed_manual'.
make[4]: Nothing to be done for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
sorry for the botherconfigure.in was messed up, and did not create
the makefile, which is why it could not make all
:-)
- -chris zubrzycki
- - --
PGP public key: http://homepage.mac.com/beren/publickey.txt
ID: 0xA2ABC070
Fingerprint: 26B0 BA6B
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On a related note, is it safe to copy a bsdos.m4 file to darwin.m4 to
get the program to compile?
- -chris zubrzycki
- - --
PGP public key: http://homepage.mac.com/beren/publickey.txt
ID: 0xA2ABC070
Fingerprint: 26B0 BA6B A409 FA83 42B3 1688 FBF9
There are new QT packages in unstable: qt2 and qt3. If you've been
having dependency problems I ask that you please give these a shot and
see if this fixes things.
What we've ended up doing is getting rid of qt altogether. qt2 and
qt3 both conflict with each other, but their -shlibs
In the release notes, the apr-2002 devel tools say that the C++ is
incompatible with the dec-2001 devel tools. Libs from one will not
link against objects from another.
How many things does installing apr-2002 actually break? And how
can it be fixed?
--
Randal L. Schwartz - Stonehenge
On Saturday, May 11, 2002, at 11:51 AM, Randal L. Schwartz wrote:
In the release notes, the apr-2002 devel tools say that the C++ is
incompatible with the dec-2001 devel tools. Libs from one will not
link against objects from another.
How many things does installing apr-2002 actually
shoot your right the only one that I didn't think of and the only one that
couldn't be avoided. See the problem is that when qt pkg was made it
should have started with qt2 and then when the first qt3 pkg was made it
should not have followed the same error as qt2 and been called qt3. So we
had
the problem is that qt was made to live in seperate directories, Not that
I want to say it but I think we should see how debian handled this to
avoid more problems. The problem with this I think will be with the bin
portion. I think that the qt2-shlibs will need qt2-bin I'm sure the
qt2-bin and
Justin Hallett wrote:
[]
had to fix it, and there was no really truly pretty way. Fink is still
young but I'd say there haven't been too many growing pains. Sorry about
the problems i believe they should all be fixed now although ppl might
still have a few problems with upgrades.
Yes, I
On Saturday, May 11, 2002, at 02:45 PM, Justin Hallett wrote:
the problem is that qt was made to live in seperate directories, Not
that
I want to say it but I think we should see how debian handled this to
avoid more problems. The problem with this I think will be with the bin
portion.
At 2:01 PM -0400 5/11/02, Chris Zubrzycki wrote:
make[1]: *** No rule to make target
`/sw/src/root-xgks-2.6-1/sw/lib', needed by
`/sw/src/root-xgks-2.6-1/sw/lib/xgksfonts'. Stop.
make: *** [fontdb/install] Error 1
### make failed, exit code 2
Failed: installing xgks-2.6-1 failed
Often this
23 matches
Mail list logo
