all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Jaft <jaft.r@outlook.com>,
	"52238@debbugs.gnu.org" <52238@debbugs.gnu.org>
Subject: [bug#52238] [PATCH] gnu: megacmd: Add mega-sdk as dependency.
Date: Sun, 13 Feb 2022 09:42:52 +0100	[thread overview]
Message-ID: <a8acc0e664273a85c2476772bca20dc59360b657.camel@gmail.com> (raw)
In-Reply-To: <DM5PR04MB377223CFF1BAC6D7074F984E99329@DM5PR04MB3772.namprd04.prod.outlook.com>

Am Sonntag, dem 13.02.2022 um 08:34 +0000 schrieb Jaft:
> > On Saturday, February 5, 2022, 12:59:47 AM CST, Liliana Marie
> > Prikler <liliana.prikler@gmail.com> wrote: 
> > Am Samstag, dem 05.02.2022 um 03:05 +0000 schrieb Jaft:
> > > In that case, I'm not sure that I have enough experience or
> > > knowledge with make tools to be able to untangle things, I'm
> > > afraid.
> > Fair enough, on the top of my head I'm not too sure how to untangle
> > this either.  However, note that mega-sdk appears pretty useless as
> > a standalone package, so I'd like to solve that issue before
> > pushing it.
> 
> That's fair; I had been first trying to get it added as a package as
> I was trying to package up MEGAsync and, as you might imagine, this
> is a dependency of it. I've nearly got the MEGAsync package working
> but need to get icons working properly, still; if I'm able to get it,
> would it make sense to send a patch here and move forward with that
> package?
Sure.  As long as there's a consumer to test that the package is
working as expected, everything ought to be fine.  I don't know which
road will be the easier one, however.




      reply	other threads:[~2022-02-13  8:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <29>
2022-02-04  0:34 ` [bug#52238] [PATCH] gnu: megacmd: Add mega-sdk as dependency Wamm K. D
2022-02-04 18:18   ` Liliana Marie Prikler
2022-02-05  3:05     ` Jaft
2022-02-05  6:59       ` Liliana Marie Prikler
2022-02-13  8:34         ` Jaft
2022-02-13  8:42           ` Liliana Marie Prikler [this message]

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=a8acc0e664273a85c2476772bca20dc59360b657.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=52238@debbugs.gnu.org \
    --cc=jaft.r@outlook.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.