Re: [Fink-devel] Virtual package handling regression

2005-02-25 Thread Martin Costabel
Daniel Macks wrote: [] Failed: Can't resolve dependency "gcc3.1" for package "prcs-1.3.2-1" (no matching packages/versions found) and the build process stopped right there before it even started. ...and then the user is completely stuck, as we well know from reading the lists. But this message c

Re: [Fink-devel] Virtual package handling regression

2005-02-25 Thread Daniel Macks
On Fri, Feb 25, 2005 at 11:38:53AM +0100, Martin Costabel wrote: > In fink-0.23.5-1, when the gcc3.1.pkg was not installed and a package > was to be built that had a BuildDepends: gcc3.1, one got the short and > unclear, but clearly visible error message > > >Failed: Can't resolve dependency "gc

[Fink-devel] Virtual package handling regression

2005-02-25 Thread Martin Costabel
In fink-0.23.5-1, when the gcc3.1.pkg was not installed and a package was to be built that had a BuildDepends: gcc3.1, one got the short and unclear, but clearly visible error message Failed: Can't resolve dependency "gcc3.1" for package "prcs-1.3.2-1" (no matching packages/versions found) and t

Re: [Fink-devel] Virtual package handling

2004-07-06 Thread Daniel Macks
On Tue, Jul 06, 2004 at 12:15:38PM -0400, Benjamin Reed wrote: > Mich?le Garoche wrote: > >Le 5 juil. 2004, ? 19:33, Daniel Macks a ?crit : > >> > >>1. When the files are not found, generate a package for system-foo > >> that has a CompileScript that gives a verbose message about where > >>to down

Re: [Fink-devel] Virtual package handling

2004-07-06 Thread Michèle Garoche
Le 6 juil. 2004, à 18:46, Alexander K. Hansen a écrit : And it shouldn't--I've swapped XFree86 for Apples's X11 on a system after Fink was installed, and have also performed a complete Fink reinstall with an XFree86-4.4 installation in place. In both cases the virtual packages got generated wit

Re: [Fink-devel] Virtual package handling

2004-07-06 Thread Michèle Garoche
Le 6 juil. 2004, à 18:27, Martin Costabel a écrit : On 6 juil. 2004, at 17:50, Michèle Garoche wrote: I've never had success in getting Apple X11 recognized when the installation of Apple X11 and its SDK was made after installing fink, be it on 10.2.8 or 10.3. A contrario, I've never had issue wh

Re: [Fink-devel] Virtual package handling

2004-07-06 Thread Alexander K. Hansen
And it shouldn't--I've swapped XFree86 for Apples's X11 on a system after Fink was installed, and have also performed a complete Fink reinstall with an XFree86-4.4 installation in place. In both cases the virtual packages got generated with not problems. On Jul 6, 2004, at 12:27 PM, Martin Cos

Re: [Fink-devel] Virtual package handling

2004-07-06 Thread Martin Costabel
On 6 juil. 2004, at 17:50, Michèle Garoche wrote: I've never had success in getting Apple X11 recognized when the installation of Apple X11 and its SDK was made after installing fink, be it on 10.2.8 or 10.3. A contrario, I've never had issue when installing them before fink. It may be that the

Re: [Fink-devel] Virtual package handling

2004-07-06 Thread Benjamin Reed
Michèle Garoche wrote: Le 5 juil. 2004, à 19:33, Daniel Macks a écrit : Okay, I'm getting mighty tired of "I can't find system-java14-dev" questions, and wondered how we could better handle these virtual packages. Currently, when VirtPackage does not find the requisite files for a given system-f

Re: [Fink-devel] Virtual package handling

2004-07-06 Thread Michèle Garoche
Le 5 juil. 2004, à 19:33, Daniel Macks a écrit : Okay, I'm getting mighty tired of "I can't find system-java14-dev" questions, and wondered how we could better handle these virtual packages. Currently, when VirtPackage does not find the requisite files for a given system-foo, the system-foo virtual

[Fink-devel] Virtual package handling

2004-07-05 Thread Daniel Macks
Okay, I'm getting mighty tired of "I can't find system-java14-dev" questions, and wondered how we could better handle these virtual packages. Currently, when VirtPackage does not find the requisite files for a given system-foo, the system-foo virtual package does not get created. That means users w