how does one go about doing so?
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourcefo
On 6/18/07, Martin Costabel <[EMAIL PROTECTED]> wrote:
> Benjamin Reed wrote:
> []
> > I agree. If the package needs headers, it should be testing for them,
> > and use them.
> >
> > If you need to fix it temporarily, fix the code to have the right -I on
> > the compile-line without a test.
> >
>
Benjamin Reed wrote:
[]
> I agree. If the package needs headers, it should be testing for them,
> and use them.
>
> If you need to fix it temporarily, fix the code to have the right -I on
> the compile-line without a test.
>
> Both are better than trying to fake up "system" headers apple probabl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander Hansen wrote:
> OK, I've gotten some feedback. How about this: I'll commit ruby
> 1.8.6 tonight, but keep ruby 1.8.5 available for a while in case of
> breakage?
Sounds good to me; 1.8.6 is supposedly a pretty good release, should be
safe
Benjamin Reed wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jean-François Mertens wrote:
>
>
>> Basically my feeling was that if a package doesn't find some headers
>> where they are and should be, it is that package's problem, and
>> should be fixed there as you just said; it wou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jean-François Mertens wrote:
> Basically my feeling was that if a package doesn't find some headers
> where they are and should be, it is that package's problem, and
> should be fixed there as you just said; it would be "wrong" to start
> copying thos
On 6/8/07, Alexander Hansen <[EMAIL PROTECTED]> wrote:
> If you're using Fink's ruby packages, please weigh in on / test out
>
> http://sourceforge.net/tracker/index.php?func=detail&aid=1706631&group_id=17203&atid=414256
>
> (ruby 1.8.6). I'd like to close that tracker item out soon.
>
> Thanks!
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jack Howarth wrote:
> Dave,
>What features do we have available in fink currently to allow
> the distribution (10.4 vs 10.5) to be tested at build time? It would
> be very useful to be able to case such things as ConfigureParms to
> have different
On 18 Jun 2007, at 16:17, Alexander K. Hansen wrote:
> I'm not particularly wedded to my package--whatever solution that
> we come up with will be fine.
>
> Ideally, it would be incumbent on the package maintainer to come up
> with a solution for an individual package, but I thought I'd put
On 6/18/07, Martin Costabel <[EMAIL PROTECTED]> wrote:
> Neil Tiffin wrote:
> > For the past couple of weeks package ksudoku will not build.
>
> A month ago, I wrote:
>
> Don't bother. This version of the ksudoku package is thoroughly rotten.
> I don't think anyone has managed to build it.
>
>
David R. Morrison wrote:
> Dear Fink developers,
>
> I have added a Distribution field to fink packages which involve
> python or perl.
But it can be used for any package, not just perl/pythonmods, right?
> As some of you will recall, we are sharing files between fink's 10.4
> and 10.5 distr
Jean-François Mertens wrote:
> On 18 Jun 2007, at 00:23, Alexander Hansen wrote:
>
>
>> We have a few packages in the distribution (often involving Tk) that
>> don't seem to build at all with a non-Apple X11, e.g. sparky-py*, due
>> to the lack of a "/usr/include/X11 -> /usr/X11R6/include/X11" s
Dave,
What features do we have available in fink currently to allow
the distribution (10.4 vs 10.5) to be tested at build time? It would
be very useful to be able to case such things as ConfigureParms to
have different values depending on whether the package was being
built under Tiger or Leopar
On 18 Jun 2007, at 00:23, Alexander Hansen wrote:
> We have a few packages in the distribution (often involving Tk) that
> don't seem to build at all with a non-Apple X11, e.g. sparky-py*, due
> to the lack of a "/usr/include/X11 -> /usr/X11R6/include/X11" symlink
> The failure mode is as follows
Neil Tiffin wrote:
> For the past couple of weeks package ksudoku will not build.
A month ago, I wrote:
Don't bother. This version of the ksudoku package is thoroughly rotten.
I don't think anyone has managed to build it.
I am CCing the maintainer. If his email still doesn't work, I hope
15 matches
Mail list logo
