all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Bavier <ericbavier@gmail.com>
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 3/4] gnu: Add xfig.
Date: Mon, 13 Oct 2014 10:17:55 -0500	[thread overview]
Message-ID: <87h9z8uhgc.fsf@gmail.com> (raw)
In-Reply-To: <20141013062313.GA16250@jocasta.intra>


John Darrington writes:

> Looking at the mass of subsitions in xfig, it seems to me that xfig is
> fighting against imake.

I would rather say that it's filling in the holes in imake's system
knowledge.

> It has been a few years since I used imake, but I seem to remember
> there was the possibility to have a "vendor" specific control file.
> In our case Guix is the vendor, so perhaps we should have a guix.cf
> file in imake.

That sounds like a nice solution.

> Perhaps it would be better to have a imake-build-system which
> generated it dynamically.

I was trying to avoid this until there was a need from more packages.
I'm not familiar with many projects that still use imake, but it appears
you might be, with your xboing patch ;)

Btw, I did push a change to xfig and transfig that should let them build
for i686 (which I tested locally now) and mips (which I don't have the
means to check locally).

-- 
Eric Bavier

Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html

  reply	other threads:[~2014-10-13 15:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10 18:19 [PATCH 3/4] gnu: Add xfig Eric Bavier
2014-10-11 22:01 ` Ludovic Courtès
2014-10-12 21:34 ` Mark H Weaver
2014-10-13  6:23   ` John Darrington
2014-10-13 15:17     ` Eric Bavier [this message]
2014-10-13 19:27       ` John Darrington
2014-10-14 21:58       ` Mark H Weaver

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

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

  git send-email \
    --in-reply-to=87h9z8uhgc.fsf@gmail.com \
    --to=ericbavier@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=john@darrington.wattle.id.au \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.