From: Roel Janssen <roel@gnu.org>
To: Mike Gerwitz <mtg@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: On packaging old versions of libraries
Date: Thu, 24 Aug 2017 00:20:34 +0200 [thread overview]
Message-ID: <87wp5uncy5.fsf@gnu.org> (raw)
In-Reply-To: <87tw0yl284.fsf@gnu.org>
Mike Gerwitz writes:
> There is a game my kids love playing named Secret Mayro
> Chronicles. Unfortunately, it's been unmaintained since 2012, and it
> was removed from Debian because it is no longer compatible with newer
> versions of libraries they package.[0] There is a maintained fork of
> the game, but it's quite different from the original (intentionally).
>
> I have the option of compiling it using old libraries (I would have to
> compile the old libraries' dependencies as well, as needed), upgrade the
> game by backporting changes from the fork (which I honestly doubt I have
> the time for right now, but I'll look into it), or run the game within a
> VM/container running an old Debian version.
>
> I'm going to look into what is required to backport, but if I decided to
> go the first route, I would probably use Guix. Would such a
> contribution be accepted considering it packages older libraries, which
> would add some cruft? At the least, I would have to compile CEGUI0.7,
> but that might need older versions of libraries itself to compile.
>
>
> [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812096
Regardless of whether older versions of libraries would be accepted
upstream, you can also keep them in a separate repository or directory
and use the environment variable GUIX_PACKAGE_PATH to include them in
your Guix.
Kind regards,
Roel Janssen
next prev parent reply other threads:[~2017-08-23 22:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 15:42 On packaging old versions of libraries Mike Gerwitz
2017-08-23 22:20 ` Roel Janssen [this message]
2017-08-24 4:35 ` Mike Gerwitz
2017-08-25 3:06 ` Eric Bavier
2017-08-25 7:07 ` Pjotr Prins
2017-08-25 3:27 ` 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=87wp5uncy5.fsf@gnu.org \
--to=roel@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mtg@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 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.