It's the NDA you agree to when you join the Apple Developer Connection,
either as an online member or as some other kind of member. I'm sure
there must be a copy somewhere at connect.apple.com .
-- Dave
---
This SF.Net email sponsored by: Fr
Dear fink developers,
As some of you know, we have a pretty slick system for generating our
web pages, using xml source which is processed into php files.
The same xml source can be processed into more "monolithic" html files,
which are distributed these days with the binary installer. Also, som
OK, the ncurses issue is another complicated one.
Both with "fixing" ncurses, and with the gcc 3.3 ABI change, we're going
to need to so what we did last time and be careful to do two things:
1) give a new version number to pkgs with C++ code when they are moved
to the 10.3 tree
2) make every depe
Hi Max.
There are really two issues here:
1) how do we ensure that our users are using the gcc version we expect?
2) how do we transition from gcc 3.1 to gcc 3.3?
I agree that we could do a much better job with #1 than we have in the past.
However, at the moment I'm more concerned about #2.
Yo
I'm still a bit unclear about what your change would accomplish, Peter.
BuildDepends is not passed to dpkg. We use that only within Fink.
As you suggest, when the shared libraries plan is fully implemented, we'll
only have to invoke something like $SHARED_DEPS in the Depends line, and
it will be
As I discussed on the list last night, I've rearranged the way we work with
the documentation and the website.
You should get rid of your CVS checkout of "web", and instead do a CVS
checkout of "xml". If you don't do this, you'll find that "make install"
no longer has the expected behavior, becau
"Alexander K. Hansen" <[EMAIL PROTECTED]> wrote:
> OK. Is this the correct operational sequence:
>
> 1) Make changes to the XML files
> 2) Commit the XML ("cvs commit xml")
> 3) Generate the PHP, HTML, etc. ("make ; make install")
> 4) Commit the other stuff ("cvs commit xml" again)
>
> ?
Dear fink-devel,
As discussed on the list a while back, I'm planning to convert four of
our essential packages (bzip2, gettext, libiconv, and ncurses) to splitoff
packages. When this is done, the -dev parts of the packages will no
longer be essential, and you'll need to declare dependencies on th
Ah, I get it now. I guess for me, a certain workaround has become such
a habit that I forgot about why I do it. Namely, when I want to build a
package foo which has a shlibs splitoff, I just do "fink build foo-shlibs"
to avoid the extra installation.
-- Dave
-
Hi Max.
If you do "fink build foo" then indeed foo-shlibs gets installed.
My understanding of the logic is this: both Depends and BuildDepends
are checked for whether they are installed or not, when "fink build foo"
is processed. Since foo-shlibs is not yet installed, the command
"fink install f
There are two ways to resolve the versioning issue. One is to rename
the package. The other is to use the relatively new "Epoch" field in
fink. All versions with epoch = 1 are regarded as newer than all
versions with epoch = 0 (the default).
Epochs should only be used in special cases, but this
Just to follow up on my own message:
As the referenced document (made publically available, with permission of
the company, by an Apple employee) indicates, Apple will be shipping
a slightly non-standard version of Perl 5.8.1, with two-level namespace
enabled and thread support turned on. For thi
The stable tree contains imlib-1.9.14-3, libjpeg-6b-6, and libpng3-1.2.5-4.
The -shlibs packages are splitoffs of the main packages, so they are
there as well.
These are precisely the same versions as are available in the unstable
tree.
-- Dave
From: Christian Schaffner <[EMAIL PROTECTED]>
Hi all. JF Mertens has contributed a number of -pm580 packages to go
along side the -pm560 packages, as well as some fixes for the latter.
You can find these in /experimental/jfmertens if you would like to
help test.
Also, he has provided workarounds for the assembler problem in the
gcc 3.3 updat
Hi Dean.
I think this is a very interesting project. I've had thoughts along similar
lines, that someday all of the basic libraries which fink is providing
might be packaged into frameworks for a more OS X-like version of fink.
-- Dave
---
John,
You'll defintely find some rough edges if you try to use fink with the
WWDC Panther preview. A number of fink developers will have access to
Panther seeds as software seed key holders, and we're working to get
fink up and running.
I found lots of problems with various 0.5.3 binary packages
Thanks for pointing this out. Fixed now.
-- Dave
> Hi,
> there is a problem on the Fink's site. Under "Documentation" section
> the link "Print Version" seems to be broken for all documents. Could
> you fix it?
>
> Thanks,
> Andrea.
> not only a wait to combine them, but the seperate them too for when
> maintainers are making the next release.
Sure. That's what I meant about needing tools. If we had a little tool
for developers to use to bundle the .info and .patch file into a text archive
(maybe with the shar format), and
Well, it still doesn't solve the problem of how to retrieve an old patch file
that correctly matches the fink version number.
Peter O'Gorman jokingly suggested on IRC using "ar" to combine them. Or maybe
it wasn't a joke? In fact, some way of combining them would be get.
(The "ar" idea is not so
gzip is not a good idea, because CVS needs text files not binary files.
-- Dave
---
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletpr
I'd like to weigh in on this again. I played around for a while today with
making shar archives out of a combination of info and patch files, using
/usr/bin/shar (which is BSD shar). The resulting file is quite similar
to the original proposal of tacking the patch file on to the info file,
but be
Hi Max. Well, actually I was thinking that fink could parse the shar
archive directly, and only unpack it if it was building a package
(in order to extract the patch file). The algorithm:
1) ignore all lines at the beginning not starting with X
2) while the line begins with an X, drop the X and
An apple employee posted the Developer Release Notes for Perl on Panther over
on the macosx-talk mailing list. They are well worth reading.
http://www.omnigroup.com/mailman/archive/macosx-talk/2003-June/013541.html
-- Dave
---
This SF.N
I don't think that -beginners is restricted either. I don't subscribe to
it, yet I am able to post to it.
-- Dave
---
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a
Finlay Dobbie <[EMAIL PROTECTED]> wrote:
> I'm not maintaining this any more.
>
> Begin forwarded message:
>
> > From: Dameron Midgette <[EMAIL PROTECTED]>
> > Date: Mon Jul 14, 2003 12:03:22 am Europe/London
> > To: <[EMAIL PROTECTED]>
> > Subject: ion-20011109-1
> >
OK, I've removed your na
On Jul 14,2003 12:08:33 -0700, William Scott <[EMAIL PROTECTED]> wrote :
>If gcc 3.3 is again responsible for this, I think fink either needs to
>fix this now or tell people not to install the patch. Merely switching
>back to 3.1 doesn't solve these problems.
>
Bill,
There have been warnings
Dear fink developers,
Over the past few weeks, I added BuildDepends on bzip2-dev, gettext-dev,
libiconv-dev and/or ncurses-dev to many many packages. The corresponding
"splitoff" versions of these essential packages have now been added to
the unstable tree, and will move to stable after a testing
There is one public source of information about 10.3: the Darwin 7 Preview
http://www.opensource.apple.com/darwinsource/7.0b1/index.html
This "includes some of the open source projects for Mac OS X", the WWDC
Panther seed.
Unless lipipx is part of a larger project, it does not seem to be on
th
Hello Mark. There are several things to do:
1) Read the installation instructions for the package: they often mention
some of the requirements.
2) Watch the output of "configure" as it runs: in many cases it will
mention things it is checking for and there might be a corresponding
fink packag
To make sure that the old issues with "Storable" don't get in the way,
people need to be updated to at least fink-0.13.0 , which changed the way
that fink handles perl modules. If people do that before trying to
upgrade Perl, they shouldn't have any problem with Storable.
Someone who upgrades Per
Hi. This is indeed a tricky problem. Ideally, people might want to have
several different versions of the perl-core packages installed, and might
want the ability to easily switch back and forth among them. So I am a
bit concerned that the "perl-core-not" packages you propose would interfere
wit
I'm not sure if you got a response to your initial message or not.
Apple has added a number of new open source pacakges with each major
release of OS X. So far, fink's philosophy has been to keep providing
a fink version of the package, even after Apple is providing their own.
(The only exception
When we need to host the tarball for a package at fink's site, it has to
be placed there by one of the fink project leaders.
If the package in question is ready to go, otherwise, please let me know
the details and I can get the tarball to the fink site.
By the way, this assumes that the source i
I'd like to get some feedback on the "splitoff" versions of the essential
packages bzip2, gettext, libiconv, and ncurses, which were introduced to
the unstable tree around 10 days ago.
Did the update go smoothly for people? Is anyone aware of any problems?
(There was one user with a problem on IR
Either way is fine. If you add your new version to the old tracker item,
be sure to change "closed" to "open". Or if you prefer to start a new
tracker item, that is fine too.
-- Dave
>
> From: Nathan Hackett <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: [Fink-devel] new version
> D
Well, to respond to my own message, a problem just showed up on the fink-users
list! As a result, there is yet another new gettext package, with the
InfoDocs command moved to the correct splitoff. I'll need to wait a while
for feedback on this one before I can move all of these things to stable.
Well, Justin just found a problem when trying to install the gettext-0.10.40-6
package: its a problem of circular dependencies. This is the same problem
which a user had reported in IRC 10 days ago.
I have removed gettext-0.10.40-6 from unstable, and put it into my
experimental tree instead. I
I also had no problem with it, or I wouldn't have put it there, of course.
But since Justin has had the mysterious "circular dependencies" problem,
I think it's important to track that down before this gets out into
userland.
-- Dave
---
This
The "circular dependencies" problem seems to have been unique to Justin's
setup, so I have returned gettext-0.10.40-6 to the unstable tree and hope
that the upgrade will go smoothly for folks.
-- Dave
---
This SF.Net email sponsored by: Free
Martin,
Ben Reed (rangerrick) is on vacation this week, so you won't be able to tap
into his experience with qt right at the moment.
-- Dave
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce,
Hi Max.
1) You are quite right, the man pages belong in -dev. I'll move them.
2) Yes, gettext-runtime and gettext-tools can be compiled completely
separately, although they use the same source (and gettext-runtime has
to be done first because gettext-tools links to the libs in the other
package)
I doubt that we can use update-alternatives in gettext. The problem is,
the update-alternatives binary is provided by dpkg, but dpkg depends
on gettext and so gettext gets built earlier in the bootstrap...
-- Dave
---
This SF.Net email spons
John,
I'm aware of this issue, and have reported it to Apple. Hopefully it will
get fixed before Panther is released.
In the meantime, adding the following two lines after "xmkmf" in your
CompileScript should fix the problem:
mv Makefile Makefile.old
sed "s|-arch i386||g" < Makefile.old > Mak
Dear Yarden,
A number of us are working on getting things ready for Panther, but due to
the NDA we don't discuss the details on the mailing list. However, you
can find a number of Panther-ready packages in various parts of the
"experimental" CVS tree.
Of course, one of the issues is simply that,
Hi Max. I need your help in figuring out the correct strategy for upgrading
gettext.
There are two issues, which I will keep separate so as not to confuse things.
As I've mentioned before, the major version number in libintl.dylib has
changed in recent versions of gettext, so we need a new gett
What happens if two packages specify the same user? Even if this is OK,
what happens if they give different info about that user?
-- Dave
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Po
Dear fink-devel,
For those of you who are helping to get Fink ready for 10.3, I've moved the
10.3-enabling code into a CVS branch of the Fink project, called
test_10_3.
Best,
Dave
---
This SF.Net email sponsored by: Free pre-built ASP.NE
Ben Hines <[EMAIL PROTECTED]> wrote:
> Why? Xcode (and 3.3) is shipping for jaguar. No need to depend on OS.
>
> -Ben
>
> On Thursday, August 14, 2003, at 08:58 AM, David R. Morrison wrote:
>
> > Modified Files:
> > ChangeLog PkgVersion.pm
> >
Dear fink developers,
As many of you know, the upgrades from gcc 2.95 to gcc 3.1 and from gcc 3.1
to gcc 3.3 cause trouble for Fink due to the change in ABI for C++ code.
For the gcc 3.1 upgrade, we made a clean break when 10.2 was released and
started using gcc 3.1 at that point. This worked re
After a discussion on IRC last night, I have a completely different proposal
to make about the gcc 3.3 upgrade.
In the new proposal we make a new distribution, perhaps called 10.2a, which
is for packages running under 10.2 but compiled with gcc 3.3. Peter O'Gorman
and others believe that version
It's possible that the problem here is the SourceForge delay in CVS: it
can take up to 24 hours for a file to propagate from the live CVS tree
to the backup CVS which is accessible to anonymous users (and through the
web interface).
-- Dave
-
One thing I forgot to say. Even with my new strategy, we need to have fink
verify that the correct version of gcc has been selected when compiling is
being done.
The overwhelming opinion on IRC last night was that fink should NOT reset
your gcc selection. Instead, fink should query the gcc selec
John Davidorff Pell <[EMAIL PROTECTED]> wrote:
> I'm actually a little confused as to why each *package* needs the gcc:
> 3.1 | 3.3 flags. Its only important to which version of gcc3 we compile
> with, not which code we compile.
> Shouldn't fink just keep track of which gcc3 a given package was
Hi. After the discussion last week, I agree with you, and don't plan to have
fink invoke gcc_select. In fact, I've put code into fink on CVS which
checks that version of gcc you are running (when it matters, as indicated
by the GCC directive), and if the version is incorrect, advises you to
run g
Pascal Bourguignon <[EMAIL PROTECTED]> wrote:
[snip]
> With the CVS HEAD it seems that clisp/configure does not take into
> account the CC environment variable: It's still using 'gcc', while in
> by script, I explicitely set export CC=3D'cc -no-cpp-precomp'.
> Obviously, since it's s
Dear Fink developers,
As some of you know, the "pkgconfig" system is being used extensively with
GNOME2 packages and possibly with other systems as well. The pkgconfig
system aims to solve the problem of multiple versions of a shared library
by (1) carefully giving different names to different ma
"Peter O'Gorman" <[EMAIL PROTECTED]> wrote:
> Hi David,
>
> On Thursday, August 28, 2003, at 09:41 PM, David R. Morrison wrote:
> >
> > SHORT TERM SOLUTION:
> > Although we should not allow a -dev splitoff to Depend on another -dev
> >
> What about fixing the fink dep engine, so that BuildDependsOnly
> packages may depend on other BuildDependsOnly, and then a kde packahe
> could BuildDepend on kdelibs3-dev and a few other -dev packages it
> needs, and fink will make sure everything needed is there; fink would
> need to recurs
Hi Peter. This one should be structured as a warning to developers, not
to users (similar to the "duplicate fields" warning). In fact, there is
already a warning if you do "fink fetch foo" and foo has no MD5-sum.
Just like with duplicate fields, and other critical errors, we shouldn't
be allowin
On Aug 29,2003 23:57:27 +0900, Peter O'Gorman <[EMAIL PROTECTED]> wrote :
>
>On Friday, August 29, 2003, at 11:41 PM, David R. Morrison wrote:
>
>> Hi Peter. This one should be structured as a warning to developers,
>> not
>> to users (similar to the
On Aug 29,2003 11:09:56 -0400, David R. Morrison <[EMAIL PROTECTED]> wrote :
>
>
>On Aug 29,2003 23:57:27 +0900, Peter O'Gorman <[EMAIL PROTECTED]> wrote :
>>
>>On Friday, August 29, 2003, at 11:41 PM, David R. Morrison wrote:
>>
>>> Hi
On Sep 5,2003 09:41:36 -0400, "Cunningham, Chad" <[EMAIL PROTECTED]> wrote :
>
>Hi,
>
>I've been making a binary of webalizer available on their site for some
>time and I'm thinking I'd rather just add it to fink and have people grab
>it from there. I've noticed that webalizer (as well as zlib,
Dear fink-devel,
I've begun to implement the gcc 3.3 update, as I described in a few messages
in mid-August.
If you are interested in testing or assisting, here's what you need to do.
First, you can bootstrap fink running 10.2 and gcc3.3 if you check out the
CVS branch tagged "test_10_3" and boo
One more thing, if you'd like to help out...
To keep things straight, when I move a package to HEAD, in the 10.2-gcc3.3
tree, I *remove* that same package from the "not_ready" branch... that
way, the only things left in the not_ready branch are the things still
being worked on...
(And in case you
This sounds like the libtool-1.4.x relinking bug. Try disabling relinking
and see if that cures it.
perl -pi.bak -e "s/need_relink=yes/need_relink=no/" ltmain.sh
is one way to do it.
Or, if it is finding an old copy of the library during linking instead
of the one it just build, you can try
Well, it's still relinking.
Why does it list as libtool
SH_LIBTOOL='/sw/share/apr-0/build/libtool'
That sounds like something already installed, perhaps by the previous build?
If it wants to be using a customized one, it should be looking in the
build directory, no?
-- Dave
---
Greg Novak <[EMAIL PROTECTED]> wrote:
> On Tue, 9 Sep 2003 Jerry Talkington wrote:
>
> > Unfortunately there doesn't seem to any desire among the maintainers to
> > make fink a more user mode environment, which is a big mistake, IMHO.
> > An application shouldn't request root privileges until abs
The 10.2-gcc3.3/stable tree is coming along nicely, and I hope to declare
"phase one" of this migration to be finished within a few days.
To this end, I would like to declare a code freeze on 10.2/stable, effective
immediately. To make sure that 10.2/stable and 10.2-gcc3.3/stable are as
close to
Put your package into /sw/fink/dists/local/main/finkinfo and fink should
find it there. (If not, check the Trees line in /sw/etc/fink.conf to
make sure that "local/main" is listed there.)
Also, you might need to fun "fink index" if fink doesn't seem to find
the package after you move it into pl
I suppose you are using the updated Developer Tools? There is a problem
with fort77 and the new tools. As it says on Fink's homepage, users
are advised not to update their developer tools, or if they do, to be
sure and run "sudo gcc_select 3" before using fink to compile packages.
The problem wi
If you are going to follow Ben's advice and bootstrap, you should probably
checkout the "test_10_3" branch from CVS rather than CVS HEAD.
-- Dave
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Dear fink-devel,
The code freeze for the 10.2/stable tree is hereby lifted. However, I would
like to ask all fink developers to try and keep 10.2-gcc3.3/stable in sync
with (or ahead of) 10.2/stable. I hope that the conversion to the new
trees will be complete within a few weeks.
All fink devel
Hello again folks.
Rob Braun has written a patch which lets us do selfupdates via rsync rather
than cvs, and the opendarwin server is currently hosting a mirror of our
cvs content which can be rsync'd.
The simplest thing to do is to simply add this as an alternative method.
But we were just discu
Here's a list of what's currently missing from 10.2-gcc3.3/stable, and a
discussion of some of the reasons.
First, KDE has not yet been moved to 10.2-gcc3.3, but no problems are
anticipated.
Second, fort77 does not compile under gcc 3.3, probably due to problems
with f2c (which probably needs so
We're still in the process of upgrading packages to be ready for gcc 3.3.
The "enforcement" of the fink declaration "GCC: 3.1" was not done in the
past, but is now being done with the recent upgrade.
Your best strategy if you are using panther is to make sure that the
dists symlink points to 10.2-
clisp-2.29 is also available from fink in binary form. The binary was
compiled with gcc 3.1.
-- Dave
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Koen, did you recompile xfree86 after the update?
-- Dave
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Fink-devel mailing list
[EMAIL PROTECTED
Dear fink-devel,
With the recent release of fink-0.14.0 and fink-0.14.1-beta, I slightly
switched strategies with respect to the various branches in CVS. I
merged the old test_10_3 branch back into HEAD at that time. Please
don't make any new commits to that branch.
Instead, what I intend to do
Does anybody have any feedback on fink 0.14.0? I'd like to move it to stable
soon, so that we can announce the rsync update method as the preferred method
for all users. (Anonymous CVS at sourceforge has become unresponsive AGAIN...)
Thanks,
Dave
---
Do you have unstable/crypto and unstable/main in the Trees line in
/sw/etc/fink.conf ? The new rsync method only updates the trees which are
mentioned in your conf file.
-- Dave
---
This SF.net email is sponsored by: SF.net Giveback Program
Sure, here's some feedback.
First, let's examine where root is actually needed in fink. We certainly
don't need to be root to run "make" on a package. Since fink directs
"make install" to a temporary installation directory, we don't need
to be root to run that either. The tricky thing, though,
I have to disagree about the timing of when root is supposed to be invoked.
I issue a command to build a package which will take an hour... I come back
two hours later, only to find that it's been waiting for the past hour for
me to enter my password? Not a good user experience.
That's why Fink
Martin,
If I uncomment that line, fink gives a circular dependency error. As is
often the case with those errors, I've been unable to track down why.
Bootstrapping from 0.14.0 should work OK.
-- Dave
---
This SF.net email is sponsored by:
Our goal is to switch Fink to Panther on October 24 or very shortly thereafter.
We've been planning the necessary changes, and working to implement them, for
months.
We still have a lot to do, and are likely to miss the release date. As
Ben said, we'll consider other major changes after we're do
I'd like to point out one feature of the current website which may not
be obvious.
A single xml file, which creates website content, is used to produce
three types of output: (1) the structured php which we use on the website
(2) "monolithic" html files, less flexible, but which we distribute on
t
> I have a problem with BuildDepends since using fink 0.14.X. I have two
> packages A and B.
> Package A does not Depend/BuildDepend on B, but B has both a Depend and
> BuildDepend on A. If I do 'fink build A B' (neither A nor B is
> installed), it builds first package A and creates the deb file
I'll be declaring a code freeze on the 10.2-gcc3.3/stable tree in the near
future, probably beginning between 12 and 24 hours from now. Once the
code freeze is in effect, if you have important changes to make to the
stable tree it may be possible, but please funnel all such change requests
through
Dear fink developers,
The code freeze on the 10.2-gcc3.3/stable tree is now in effect. You are
free to modify other trees, and in particular, there is still work to
be done on the 10.2-gcc3.3/unstable tree.
I'll announce here when the code freeze is lifted.
-- Dave
-
Here's an update on the current state of the 10.3 tree.
Currently, the 10.3 tree has only a very few things in it. A few are
"placeholder" packages which allow fink to use some new components of
the system in 10.3 which were not present in 10.2. Others are 10.3-specific
revisions of packages.
I
> That would be pretty tough to do on 10.3 since most of the dependencies
> aren't in the 10.3 tree yet. I'd have to move all them over. If you
> want that help, you should move the working packages into the 10.3 tree
> now.
>
> Anyway, waiting makes it too difficult for me to contribute, so I
Martin,
That warning would be more easily understood if it were worded differently.
Instead of "prebinding not disabled because foo overlaps with bar" it
should say "prebinding not disabled even though foo overlaps with bar".
Normally, an overlap would cause the linker not to prebind, but we're
te
We're pleased to announce that Peter O'Gorman has joined the Fink admin
team, which still includes Max Horn, Ben Reed, and myself. We've also
set up a mailing address with which you could reach the four of us,
should you need to: [EMAIL PROTECTED] .
-- Dave Morrison
--
Hi Jean-Francois.
My guess is that what happens is this: the configure script for some
package runs "which perl" and then uses the answer to decide what to
write in the perl scripts for that package. dpkg must be one of the
things affected by this.
Since we don't have BuildConflicts implemented
> Shouldn't system-perl simply put in a /usr/bin/perl -> /sw/bin/perl symlink?
> That seems much easier.
Unfortunately, that runs contrary to fink's policy of not modifying /usr
but confining itself to /sw (with the sole exception of a fink-installed
xfree86).
-- Dave
Dear fink-devel,
I got the following message from a user who is running tetex on 10.3.
The setsid error message is very mysterious. Does anybody have any
idea what could cause this? Could it be related to the changes in
default permissions in 10.3?
(What's happening here is that xdvi calls /sw/
If A Depends on B, and B Depends on C, then you do not have to state a
dependency of A on C since C will always be present when A is.
However, if A BuildDepends on B and B BuildDepends on C, then you *cannot*
assume that C is present when A is being built. (If B has never been
built before then i
> No, rather the texinfo package should be updated.
This has been on my to-do list for a while.
Recent versions of texinfo require recent versions of gettext. Since the
newest gettext has a binary compatibility change from fink's gettext,
we need a gettext2 package in order to update texinfo. T
Dear fink developers,
I've just spent 10 minutes chasing down the cause of a bug report I received
from a user.
Here's the cause: somebody edited one of my packages in 10.3/unstable,
removing the dlcompat dependency and increasing the revision number by 10.
Unfortunately they did not change the
Just a followup to my previous message. I've now noticed that the only
change which was made to the package was to remove a BuildDepends on
dlcompat, not a Depends. That shouldn't have required a change to the
revsion number at all!!!
-- Dave
-
Hi Peter.
If I understand correctly, any package which links to dlcompat will build
differently under 10.2 and 10.3, regardless of what dependencies are
specified. Both dlcompat and dlcompat-dev are placeholders in 10.3,
are they not?
So, since the package in question was already in 10.3, anyone
301 - 400 of 1507 matches
Mail list logo
