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
Subject: [bug#52238] [PATCH] gnu: Add MEGA SDK
Date: Mon, 06 Dec 2021 20:52:59 +0100	[thread overview]
Message-ID: <a7ef0719459f095dfe41bb3d12a5d77530c195bd.camel@gmail.com> (raw)
In-Reply-To: <DM6PR19MB2460DBB2D05A4BF1FA3795BD99699@DM6PR19MB2460.namprd19.prod.outlook.com>

Am Donnerstag, den 02.12.2021, 06:32 +0000 schrieb Jaft:
> * gnu/packages/mega.scm (mega-sdk):Add MEGA SDK
Should be "New variable."

> The SDK is a dependency of MEGAsync so I thought to make a new file
> since there's multiple packages that are MEGA related and then I
> discovered that the megacmd package exists; is it better for this to
> be placed in sync.scm, next to megacmd?
Sync is good.  If existing Mega packages use the SDK, try to unbundle
them.

> ---
I don't know if I told you that yet, but comments ought to go below
this line.

> +(define-public mega-sdk
> +=C2=A0 (let ([version "3.9.10"])
> +=C2=A0=C2=A0=C2=A0 (package
> +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (name "mega-sdk")
I hate you too, Outlook.

> +(define-public mega-sdk
> +  (let ([version "3.9.10"])
Guile is not Racket, we use uniform brackets.
> +    (package
> +      (name "mega-sdk")
> +      (version version)
There's no reason to let-bind version if you're just going to assign it
here anyway.
> +      (source (origin
> +                (method git-fetch)
> +                (uri (git-reference
> +                      (url "https://github.com/meganz/sdk/")
> +                      (commit (string-append "v" version))))
> +                (file-name (git-file-name name version))
> +                (sha256 (base32
> +                         
> "08qw23rm4rrvlsbcixrncbi5x0qgqkpx74l5f1gq2rgll0ksx8ph"))
> +                (modules '((guix build utils)))))
> +      (build-system gnu-build-system)
> +      (native-inputs `(("autoconf" ,autoconf)
> +                       ("automake" ,automake)
> +                       ("libtool" ,libtool)))
> +      (inputs `(("crypto++" ,crypto++)
> +                ("zlib" ,zlib)
> +                ("sqlite" ,sqlite)
> +                ("openssl" ,openssl)
> +                ("c-ares" ,c-ares)
> +                ("curl" ,curl)
> +                ("freeimage" ,freeimage)
> +                ("readline" ,readline)
> +                ("libsodium" ,libsodium)))
> +      (arguments `(#:tests? #f))
Never leave #:tests? #f uncommented.
> +      (home-page "https://mega.nz/sdk")
> +      (synopsis "SDK for the MEGA service, offered by MEGA Limited")
Sponsored by RAID: Shadow Legends.
> +      (description "A low-level SDK for the MEGA service which
> powers the
> +file-sharing site.  This package provides two executables:
> +@itemize
> +@item megacli: a command-line tool that allows usage of all SDK
> features
> +@item megasimplesync: a command line tool that allows usage of the
> +synchronization engine
> +@end itemize")
> +      (license license:bsd-2))))
Given the megacli command, what's the relation to existing MEGA
packages, particularly megacmd?

Cheers





  reply	other threads:[~2021-12-06 19:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1136809883.7440498.1638426746315.ref@mail.yahoo.com>
2021-12-02  6:32 ` [bug#52238] [PATCH] gnu: Add MEGA SDK Jaft
2021-12-06 19:52   ` Liliana Marie Prikler [this message]
2021-12-17 22:30     ` Jaft
2021-12-17 23:22       ` Liliana Marie Prikler
2021-12-18  5:14         ` Jaft
2021-12-18  7:47           ` Liliana Marie Prikler
2021-12-20  1:58             ` Jaft
2021-12-20 20:08               ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a7ef0719459f095dfe41bb3d12a5d77530c195bd.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.