On Thu, 6 Jul 2017 19:58:39 -0500, Hanspeter Niederstrasser  wrote:

> On 7/6/17 8:09 AM, Martin Costabel wrote:
> > 
> > There is a bug in how the new guile20 names its files:
> > 
> > % ls /sw/bin/guile*2.0*
> > /sw/bin/guile-2.0        /sw/bin/guile-config-2.0    
> > /sw/bin/guile-snarf-2.0 /sw/bin/guile-tools-2.0
> > 
> > In particular guile-config-2.0 should be guile-2.0-config as it used to 
> > be in the previous version. Some parts of guile20 itself think so, too:
> > 
> > % ls -l /sw/share/guile/2.0/scripts/binoverride
> > total 32
> > lrwxr-xr-x  1 root  admin  17 Jul  6 14:20 guile -> /sw/bin/guile-2.0
> > lrwxr-xr-x  1 root  admin  24 Jul  6 14:20 guile-config -> 
> > /sw/bin/guile-2.0-config
> > lrwxr-xr-x  1 root  admin  23 Jul  6 14:20 guile-snarf -> 
> > /sw/bin/guile-2.0-snarf
> > lrwxr-xr-x  1 root  admin  23 Jul  6 14:20 guile-tools -> 
> > /sw/bin/guile-2.0-tools
> > 
> > Thus packages that use this binoverride    mechanism (which may well be 
> > outdated, but wasn't broken until recently) cannot find guile-config and 
> > will fail.
> > 
> > I am not sure who feels responsible for the guile20 package nowadays.
> 
> The change from guile-2.0-config to guile-config-2.0 is my fault.  When 
> 2.0.14 was released, I noticed that %p/bin/guild (already present in 
> 2.0.12) was not versioned using the --program-transform-name in 
> ./configure [1].  But the alternative flag --program-suffix did version 
> everything in %p/bin [2]. So I updated the guile20.info to use the 
> --program-suffix flag. However, I did not notice that the placing of the 
> -2.0 token changed, and this broke the symlinks in binoverride.
> 
> [1] http://paste.lisp.org/display/350172
> [2]  
> http://fink.cvs.sourceforge.net/viewvc/fink/dists/10.9-libcxx/stable/main/finkinfo/languages/guile20.info?r1=1.3&r2=1.4
> 
> At the time, I decided to not just manually rename bin/guild to 
> bin/guild-2.0 because I was not sure if there was any code directed to 
> the actual file name or if it was just a file rename (guile-2.0-tools 
> points to the unversioned guild in the 2.0.12 deb).
> 
> So the options are to
> 1) return to the old file names/configure flag and manually versionize 
> guild (and fix the bin/guile-2.0-tools symlink), or
> 2) fix our unversioned symlinks in binoverride to point to the new 
> guil*-2.0 names in %p/bin.
> 
> I don't know which is better for guile functionality.
How about going back to --program-transform-name but having it also act on 
bin/guild? That way we can have #1 (which is consistent with guile18) but have 
it done by the native build system (in case it does more than just a simple 
file rename). Something like:

--program-transform-name="s|guile|guile-2.0|g; s|guild|guild-2.0|g"

The rev-up (for whatever solution is chosen) would be also be a good chance to 
switch guile20 to readline7.

 dan

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
https://sourceforge.net/p/fink/mailman/fink-users/
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to