From: ludo@gnu.org (Ludovic Courtès)
To: "Taylan Ulrich \"Bayırlı/Kammer\"" <taylanbayirli@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add higan.
Date: Wed, 08 Jun 2016 14:37:32 +0200 [thread overview]
Message-ID: <87porrkgab.fsf@gnu.org> (raw)
In-Reply-To: <87fustalcn.fsf@T420.taylan> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Sat, 04 Jun 2016 02:44:40 +0300")
taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
> Some things to note about this package & questions:
>
> - There's no official VCS repo and the author doesn't want automated
> tools to download files from his homepage; there's an unofficial git
> repo at GitLab but I found it unsuitable so I'm hosting the sources
> specifically for Guix at GitHub now:
>
> https://github.com/TaylanUB/higan
In what sense is it unsuitable? It’s OK to have a couple of patches,
but it’s not quite OK to host a fork of the upstream package, IMO (at
the very least, it can create confusion and make it harder to see how it
differs from the “real” package.)
> - I forgot if there's a guideline for this: the release versions are
> called 'v097', 'v098' etc. with always a 'v' in front. Should that
> 'v' appear in the version field of the package or should it be
> stripped?
I’d strip it.
> - As seems to be tradition among emulator developers, the build system
> and the program's handling of the file system are a big pile of poo,
> so:
>
> * Is it principally OK to reuse the standard `build' and `install'
> phase procedures a second time, just with the CWD changed, as I do
> here?
It’s OK, though I often find it clearer to use
‘with-directory-excursion’ so that we can more easily reason about the
current directory.
> * The program insists on looking in ~/.local/share for some data files
> that are actually installed in $prefix/share; does my strategy here
> look OK, in that I wrap the executable to copy the data files into
> ~/.local/share every time the program is run?
Sounds like a sledgehammer no? :-)
If those files are immutable, what about patching Higan to look for
those files in $datadir instead?
Thanks, and sorry for the delay!
Ludo’.
next prev parent reply other threads:[~2016-06-08 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 23:44 [PATCH] gnu: Add higan Taylan Ulrich Bayırlı/Kammer
2016-06-07 15:28 ` Taylan Ulrich Bayırlı/Kammer
2016-06-07 18:29 ` Efraim Flashner
2016-06-07 19:08 ` Taylan Ulrich Bayırlı/Kammer
2016-06-08 12:37 ` Ludovic Courtès [this message]
2016-06-08 13:21 ` Taylan Ulrich Bayırlı/Kammer
2016-06-08 15:27 ` Ludovic Courtès
2016-06-09 20:43 ` Taylan Ulrich Bayırlı/Kammer
2016-06-10 12:56 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87porrkgab.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=taylanbayirli@gmail.com \
/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.