Re: [Fink-devel] Tiger build report

On May 3, 2005, at 09:41, Benjamin Reed wrote: OK. Your previous mail made it sound like that was not the case. Assuming you never heard back before, I'd say maybe ping the maintainer again, and if you don't hear anything in a few days, go ahead and put it in, if the current package is causi

Re: [Fink-devel] Tiger build report

Le 3 mai 2005 à 15:41, Benjamin Reed a écrit : Michèle Garoche wrote: People don't mess with other people's experimental, generally. ??? I was told that experimental was precisely here to do that. Provides a location where to put some attempt other people can test or change. So, now what is e

Re: [Fink-devel] Tiger build report

Michèle Garoche wrote: People don't mess with other people's experimental, generally. ??? I was told that experimental was precisely here to do that. Provides a location where to put some attempt other people can test or change. So, now what is experimental for? experimental/ is for your own t

Re: [Fink-devel] Tiger build report

Le 3 mai 2005 à 14:22, Benjamin Reed a écrit : Michèle Garoche wrote: For doxygen, there had been a newer version in experimental/ michga for 2 months now. People don't mess with other people's experimental, generally. ??? I was told that experimental was precisely here to do that. Provides a l

Re: [Fink-devel] Tiger build report

Michèle Garoche wrote: For doxygen, there had been a newer version in experimental/michga for 2 months now. People don't mess with other people's experimental, generally. If you've got a fix, feel free to release it (or pass it on to the maintainer, if it's not yours). :) ---

Re: [Fink-devel] Tiger build report

Le 2 mai 2005 à 22:45, Matthew Sachs a écrit : I've done a build of the entire Fink unstable tree on Tiger with GCC 4 using package descriptions as of 2005-04-30. The report is at: Package maintainers who want to see if their package builds

Re: [Fink-devel] Tiger build report

Le 2 mai 2005 à 22:45, Matthew Sachs a écrit : I've done a build of the entire Fink unstable tree on Tiger with GCC 4 using package descriptions as of 2005-04-30. The report is at: Package maintainers who want to see if their package builds

Re: [Fink-devel] Tiger build report

Le 2 mai 2005 à 22:45, Matthew Sachs a écrit : I've done a build of the entire Fink unstable tree on Tiger with GCC 4 using package descriptions as of 2005-04-30. The report is at: Package maintainers who want to see if their package builds

Re: [Fink-devel] Tiger build report

On May 2, 2005, at 17:09, Hisashi T Fujinaka wrote: What about sorting by maintainer? I've implemented this: http://www.zevils.com/fink/2005-04-30/maintindex.html and linked it from the main report summary. --- This SF.Net email is sponsored b

Re: [Fink-devel] Tiger build report

On May 2, 2005, at 17:19, Trevor Harmon wrote: On May 2, 2005, at 2:09 PM, Hisashi T Fujinaka wrote: What about sorting by maintainer? Sorting by package name would be nice, too. That's already in there: http://www.zevils.com/fink/2005-04-30/pkgindex.html The link to it is at the top of report.

Re: [Fink-devel] Tiger build report

On May 2, 2005, at 2:09 PM, Hisashi T Fujinaka wrote: What about sorting by maintainer? Sorting by package name would be nice, too. Thanks to an unnamed bookseller, my Tiger hasn't been shipped yet, but I could take a look at my packages. Why the confidentiality? I don't see any reason to protect

Re: [Fink-devel] Tiger build report

On Mon, 2 May 2005, Matthew Sachs wrote: I've done a build of the entire Fink unstable tree on Tiger with GCC 4 using package descriptions as of 2005-04-30. The report is at: Package maintainers who want to see if their package builds on Tige