Peter O'Gorman writes:
Benjamin Reed wrote:
Tom Emerson wrote:
Greetings,
I see on http://fink.sourceforge.net/pdb/nomaintainer.php that the
Guile and Flex packages need a maintainer. I'm interested in doing
this, if no one else has taken them on.
I can't speak for Guile,
I grok the reason to keep around the different flex versions. But why
the older guile?
When a package supplies shared libraries, and the version of the shared
libraries changes in an update to the package, we keep the old package
around so that the old shared libraries are still available for
For everyone emailling me telling me it's not working, PLEASE update
fink from cvs before you email me, and I mean fink it's self not the
package descriptions...
Preparing to replace libmng2 1.0.6-1 (using
.../libmng2_1.0.6-1_darwin-powerpc.deb) ...
Unpacking replacement libmng2 ...
Preparing
Justin,
Fink 0.20.0 was released about 1 week ago. Does your package work with
0.20.0? I hope so, because very few users understand how to update
fink from CVS. If we need to make a bugfix release of 0.20.1 to address
some particular problem, please let me know.
-- Dave
To: Fink devel
David R. Morrison wrote:
Justin,
Fink 0.20.0 was released about 1 week ago. Does your package work with
0.20.0? I hope so, because very few users understand how to update
fink from CVS. If we need to make a bugfix release of 0.20.1 to address
some particular problem, please let me know.
I have
On Apr 9, 2004, at 2:21 PM, Martin Costabel wrote:
I have tried to compile libmng2 with different versions of fink in
order to reproduce the error that was reported. I never managed to see
the error. It always built correctly. Justin, could you explain what
was the problem?
See the thread
Koen van der Drift wrote:
See the thread on this subject in fink-users for the console output with
the error.
I have seen the error messages, but thesin seems to be the only person
who understands what is going on, so I would appreciate if he could explain.
--
Martin
I grok the reason to keep around the different flex versions. But why
the older guile?
The older guile is creating problems for me if both it and 16 are
installed simultaneously. I am trying to compile a program that I am
trying to port and package for fink and I can't get it to see the new
William Scott wrote:
I grok the reason to keep around the different flex versions. But why
the older guile?
The older guile is creating problems for me if both it and 16 are
installed simultaneously. I am trying to compile a program that I am
trying to port and package for fink and I can't
Hi Martin,
If you want to test the bluefish variants, the info and patch files are
in the tracker now. I've tested them with old version installed, and it
updates correctly, one can switch from bluefish-gnome2 to bluefish and
vice-versa too. Only one version is installed at one time.
As there
yes it was fixed before the release of 0.20.0 unless 0.20.0 wasn't
taken from HEAD. dmacks fixed it in HEAD and it hasn't been broken
since, and I can buil dlibmng fine with fink cvs, I've built it 20
times in a row now and it never fails.
---
TS
http://southofheaven.org
Chaos is the beginning
the problem was with the order of splitoffs, dmacks added the ability
to have none consecutive SplitOffN fields in info files, when he did
this he accidentally reversed to order in which they built the deb
files, so if SplitOff had lib/lib%N.*.dylib in the Files: field and
SplitOff2: had lib
12 matches
Mail list logo