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 17:27:35 +0200 [thread overview]
Message-ID: <87k2hzem54.fsf@gnu.org> (raw)
In-Reply-To: <87fusn7r5i.fsf@T420.taylan> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Wed, 08 Jun 2016 16:21:13 +0300")
taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
[...]
>> 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.)
>
> The repo is just for having a consistent place from which the source can
> be fetched, as the author doesn't want source bundles to be downloaded
> from his website. No changes to the code are made.
>
> The repo at GitLab didn't seem to tag releases properly. That being
> said, now that I look at it, it seems more like an oversight for v098.
> Other releases seem to be tagged quite consistently:
>
> https://gitlab.com/higan/higan/tags
>
> Should we use that repo instead? It's a bit more official than mine.
Yes, I think it would be more appropriate.
>>> * 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?
>
> Apparently, the files that are part of the distribution are pure data
> files, i.e. fine to be read-only. However, the directory hierarchy of
> which they're a part needs to be writable, as higan creates further
> files there. With that cp -r, the directory hierarchy is made sure to
> be there, and the data files made sure to be up to date.
>
> Although I didn't look too closely at the sources, patching higan to do
> things differently would presumably be a nontrivial task, since it seems
> bent on doing things in terms of this directory structure that contains
> both pure data and read-write data files.
Hmm OK. What do other distros do?
Thank you!
Ludo’.
next prev parent reply other threads:[~2016-06-08 15:27 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
2016-06-08 13:21 ` Taylan Ulrich Bayırlı/Kammer
2016-06-08 15:27 ` Ludovic Courtès [this message]
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
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=87k2hzem54.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 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).