From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add android-tools.
Date: Thu, 8 Sep 2016 11:27:10 +0200 [thread overview]
Message-ID: <57D12EEE.609@crazy-compilers.com> (raw)
In-Reply-To: <87wpivzeex.fsf@gnu.org>
Hi,
some remarks:
+ (source (origin
+ (method url-fetch)
+ (uri (string-append
+ "https://launchpad.net/ubuntu/+archive/primary/+files/"
Is this the original source? I'd expact this to come from Google or AOSP?
+ name "_" version
+ ".orig.tar.xz"))
Should be on the same line.
+ (patches (search-patches "android-tools-patches.patch"
+ "android-tools-makefiles.patch"))
+ (for-each (lambda (file)
+ (copy-file (string-append "core/" file "/" file)
+ (string-append bin file)))
+ '("adb" "adbd"
+ ;; "fastboot"
+ ))))))))
Look like some are missing here? You are building four sub-packages
install only two binaires? Maybe you want to use (find-files "bin" ".*")
? And maybe (install-file …) simplifies the code.
+ (synopsis "Android Tools")
"Tools" is very generic. Please be more verbose here. Which kind of tools? What is their purpose?
+ (description
+ "Android Debug Bridge (adb) is a versatile tool lets you manage the state
Please a short summary of included stuff/tools and maybe make the list into a @{itemize}.
Regarding the patches: It looks like they add the vast parts of the Makefile, which is very curious. Why are they needed? (Please add as a comment to the package definition).
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
prev parent reply other threads:[~2016-09-08 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 18:02 [PATCH] gnu: Add android-tools Jan Nieuwenhuizen
2016-09-08 9:27 ` Hartmut Goebel [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=57D12EEE.609@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@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.