unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: 18033@debbugs.gnu.org
Cc: John Darrington <jmd@gnu.org>
Subject: bug#18033: Add support for 'search-path-specifications' referring to files
Date: Wed, 16 Jul 2014 16:02:20 +0200	[thread overview]
Message-ID: <87k37dh05v.fsf_-_@gnu.org> (raw)
In-Reply-To: <20140716100854.GB21262@jocasta.intra> (John Darrington's message of "Wed, 16 Jul 2014 12:08:54 +0200")

See use case below.

John Darrington <john@darrington.wattle.id.au> skribis:

> On Wed, Jul 16, 2014 at 11:23:12AM +0200, Ludovic Court??s wrote:
>      John Darrington <john@darrington.wattle.id.au> skribis:
>      
>      > On Tue, Jul 15, 2014 at 10:59:17PM +0200, Ludovic Court??s wrote:
>      
>      [...]
>      
>      >      The problem is that ???search-path-specification??? is meant for $PATH-like
>      >      variables that list directories, not files.
>      >
>      > That occurred to me too.  But what problems does it actually cause?
>      
>      That we can???t use it for $XML_CATALOG_FILES.
>      
>      >      So I see two solutions:
>      >      
>      >        1. Patch libxml2 so that it honors a new variable, say
>      >           $XML_CATALOG_DIRECTORIES, which would allow us to use
>      >           ???search-path-specification???.
>      >      
>      >        2. Augment support for search paths to allow file-based search paths.
>      >      
>      >      (2) may be best in the long run, but it has ramifications in different
>      >      places.
>      >      
>      >
>      > (1) seems like a good idea only if upstream can be persuaded to adopt it.
>      
>      Which is unlikely, given that it???s redundant with $XML_CATALOG_FILES.
>      
>      > What are the ramifications of (2) ?
>      
>      There are changes in the build tools, for instance ???search-path-as-list???
>      (used by ???set-path-environment-variable???, used in gnu-build-system.scm)
>      expects directories, not files.  And all this calls things
>      ???directories???.
>      
>      This is a change we could schedule for the next core-updates.
>
> This sounds like it is the most sensible solution. 
>
> J'

       reply	other threads:[~2014-07-16 14:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1405449096-29230-1-git-send-email-jmd@gnu.org>
     [not found] ` <1405449096-29230-5-git-send-email-jmd@gnu.org>
     [not found]   ` <87r41ml4nu.fsf@gnu.org>
     [not found]     ` <20140715214338.GB16482@jocasta.intra>
     [not found]       ` <87mwc9irnj.fsf@gnu.org>
     [not found]         ` <20140716100854.GB21262@jocasta.intra>
2014-07-16 14:02           ` Ludovic Courtès [this message]
2014-12-27 11:26             ` bug#18033: Add support for 'search-path-specifications' referring to files Ludovic Courtès
2014-12-27 22:57               ` Ludovic Courtès
2015-01-02 23:30                 ` Mark H Weaver
2015-01-03 18:48                   ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k37dh05v.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=18033@debbugs.gnu.org \
    --cc=jmd@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).