From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: "Wamm K. D" <jaft.r@outlook.com>, 52238@debbugs.gnu.org
Subject: [bug#52238] [PATCH] gnu: megacmd: Add mega-sdk as dependency.
Date: Fri, 04 Feb 2022 19:18:44 +0100 [thread overview]
Message-ID: <c9a435f4161567be30534b430ecbe192fcb3943a.camel@gmail.com> (raw)
In-Reply-To: <DM5PR04MB377212270DC40C9C37EFAFC699299@DM5PR04MB3772.namprd04.prod.outlook.com>
Am Donnerstag, dem 03.02.2022 um 18:34 -0600 schrieb Wamm K. D:
> * gnu/packages/sync.scm (megacmd): Use new package mega-sdk as
> dependency
> rather than build mega-sdk via building recursively.
> ---
> gnu/packages/sync.scm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gnu/packages/sync.scm b/gnu/packages/sync.scm
> index 52003a7c9d..753b4e4d47 100644
> --- a/gnu/packages/sync.scm
> +++ b/gnu/packages/sync.scm
> @@ -281,8 +281,7 @@ (define-public megacmd
> (method git-fetch)
> (uri (git-reference
> (url "https://github.com/meganz/MEGAcmd")
> - (commit (string-append version "_Linux"))
> - (recursive? #t)))
> + (commit (string-append version "_Linux"))))
> (sha256
> (base32
> "004j8m3xs6slx03g2g6wzr97myl2v3zc09wxnfar5c62a625pd53"))
> @@ -301,6 +300,7 @@ (define-public megacmd
> ("curl" ,curl)
> ("freeimage" ,freeimage)
> ("gtest" ,googletest)
> + ("mega-sdk" ,mega-sdk)
> ("openssl" ,openssl)
> ("pcre" ,pcre)
> ("readline" ,readline)
Note that the hash didn't change, so you're still fetching the
recursive version. In addition, the non-recursive version won't build
as mega-sdk is deeply bundled into megacmd.
next prev parent reply other threads:[~2022-02-04 18:28 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 [this message]
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
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=c9a435f4161567be30534b430ecbe192fcb3943a.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 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).