Alexander Strange wrote:
What version of fink is it (fink --version)?
Current stable and unstable both have 0.20.2-1 which supports this.
Hmmm. This doesn't seem normal, then -- I have a very old fink even if I
have "current" FINK:
[EMAIL PROTECTED]:~]$ fink --version
Package manager version: 0.1
On May 31, 2004, at 10:10 PM, Rohan Lloyd wrote:
You're not the only one. I get exactly the same results here.
--
Rohan Lloyd
Oh, now it's missing for me too. It must have disappeared when I went
from 0.20.1.cvs to 0.20.2.
---
This SF.Net email
Alexander Strange wrote:
[]
Current stable and unstable both have 0.20.2-1 which supports this.
Cvs log shows that dumpinfo is not in the released versions of fink:
RCS file: /cvsroot/fink/fink/perlmod/Fink/Engine.pm,v
Working file: Engine.pm
head: 1.176
[]
symbolic names:
release_0_20_2: 1
the recode package is still in the unstable tree and has no maintainer.
I would like to contribute my skills to the fink project and become a
code maintainer :D
Varun Mehta
---
This SF.Net email is sponsored by: Oracle 10g
Get certified on th
On 1 Jun 2004, at 12:06 PM, Nigel Stanger wrote:
On 1/6/2004 1:59 PM, Alexander Strange at [EMAIL PROTECTED] spake
thus:
What version of fink is it (fink --version)?
Current stable and unstable both have 0.20.2-1 which supports this.
nuevorico> fink --version
Package manager version: 0.20.2
Distr
On May 31, 2004, at 9:58 PM, Nigel Stanger wrote:
On 1/6/2004 1:37 PM, Alexander Strange at [EMAIL PROTECTED] spake
thus:
It's easier to do 'fink dumpinfo '; this prints the revision
and path to .info file.
Huh?!?
nuevorico> fink dumpinfo pcrs0
fink: unknown command "dumpinfo".
Type 'fink --help'
On May 31, 2004, at 9:07 PM, Ben Hines wrote:
Also don't know if you tried it but you can usually just run 'fink
index' to kick the indexer sometimes. But upping the rev is a good way
to tell what fink is actually using.
-Ben
It's easier to do 'fink dumpinfo '; this prints the revision
and pat
David H. wrote:
All of those _cannot_ run with the Apple supplied Apache, you have to
build the Fink version and use it as well.
That is a very strict rule we stick to, so it is highly unlikely your
package would be accepted the way you are providing it now.
I hope that helps :)
Thanks! I was e
On May 31, 2004, at 1:39 PM, Martin Langhoff (NZL) wrote:
Ben Hines wrote:
Works fine here, with those info files. (the patch fails, though)
Perhaps you have an old version of your info file there somewhere. If
all else fails try putting the revision on 2 and see if 'fink update'
updates it to 2
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Martin Langhoff (NZL) wrote:
Is this within fink policy? What alternatives do I have in making this
module compliant?
No. You are not allowed to install _anything_ outside of /sw-
There is one exception which is some special case when handling A
The package I am building is libapache-mod-midgard. Now, the module is
built against MacOSX's native Apache, using APXS. So far, I am patching
the Makefile to have the module installed in /sw/lib.
To allow integration with the OS X default Apache install I will provide
a separate script that a
Ben Hines wrote:
Works fine here, with those info files. (the patch fails, though)
Perhaps you have an old version of your info file there somewhere. If
all else fails try putting the revision on 2 and see if 'fink update'
updates it to 2.
Thanks! Bumping the revision helped. Is this a fink bug,
> Sorry for jumping on this, but did you keep a note of what was missing from
> where? If you could inform the maintainers of missing BuildDepends it would
> help a lot.
Sorry, but the list is quite incomplete and outdated.
---
This SF.Net em
AIDA Shinra wrote:
The problem is library-to-library dependency. For example, every
applications depending on gtk+2 must also depend on atk1, glib2-dev,
pango1-xft2-dev, gettext-dev and libiconv-dev. This is major source of
error. When Todai Fink Team runned a script like this in April:
for pkg in
AIDA Shinra <[EMAIL PROTECTED]> wrote:
> Let A a library depending on neon. If A-shlibs and A-dev has been built
> with neon23, A-dev and neon24 should not be installed at the same
> time. If both were installed, binary inconsistency happens:
>
> gcc -o B B.o -lA -lneon
>
> If B did not directly
> If B did not directly refer any neon's symbols,
>
> gcc -o B B.o -lA -lneon
Oh, this line is:
gcc -o B B.o -lA
---
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take a
> An example is the "neon" package. Currently we are using neon24, but
> in the recent past we used neon23 (and many earlier ones). If you have
> neon24 installed and link with -lneon, you will be linked to the
> v. 24 of the neon lib because of a symlink from libneon.dylib to
> libneon.24.dylib.
Leonida wrote:
David H. wrote:
If you see a web-site that might be interested in reporting in depth
about Fink, tell me.
http://freesmug.mine.nu:8200/tutorial/fink/
I am forwarding this to the fink-devel list for those who don't read
fink-beginners. It is amazing, particularly the movies about i
18 matches
Mail list logo
