unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: 36411@debbugs.gnu.org
Subject: [bug#36411] [PATCH] gnu: Add libresprite.
Date: Sat, 29 Jun 2019 10:39:30 -0400	[thread overview]
Message-ID: <87mui0lal9.fsf@dustycloud.org> (raw)
In-Reply-To: <87mui1flpv.fsf@sdf.lonestar.org>

Jakob L. Kreuze writes:

> swedebugia <swedebugia@riseup.net> writes:
>
>>> The bundled libraries is an issue with 'aseprite' as well. I'll see
>>> about submitting a separate patch to resolve it there.
>>
>> +1
>
> Though, after looking at it, I'm realizing that this involves about
> three new packages, as well as some minor patches upstream. I think I'll
> still work towards unbundling libraries, but it will take some time.

I don't think this needs to be a blocker on merging libresprite if it
wasn't a blocker on merging aesprite.  How about filing a separate bug
for that so we don't forget, then we can just worry about getting this
one in?

I wonder also if there are any significant benefits to keeping aesprite
around if we have libresprite.  What do you think?  Maybe aesprite could
become an alias for the new libresprite.  Thoughts?

  reply	other threads:[~2019-06-29 14:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28  0:43 [bug#36411] [PATCH] gnu: Add libresprite Jakob L. Kreuze
2019-06-28  5:28 ` swedebugia
2019-06-28 14:05   ` Jakob L. Kreuze
2019-06-28 15:51     ` swedebugia
2019-06-28 21:23       ` Jakob L. Kreuze
2019-06-29 14:39         ` Christopher Lemmer Webber [this message]
2019-06-30  0:45           ` Jakob L. Kreuze
2019-06-29 15:27     ` Tobias Geerinckx-Rice
2019-06-29 17:10       ` swedebugia
2019-06-30  0:49       ` Jakob L. Kreuze
2021-11-21 23:03 ` bug#36411: " Julien Lepiller

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=87mui0lal9.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=36411@debbugs.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).