unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <contact.ng0@cryptolab.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 25728@debbugs.gnu.org
Subject: bug#25728: [PATCH 2/2] gnu: Add colorforth.
Date: Sat, 15 Apr 2017 15:28:43 +0000	[thread overview]
Message-ID: <20170415152843.2vyk7uhycuny5rov@abyayala> (raw)
In-Reply-To: <871suvu8yu.fsf@elephly.net>

Ricardo Wurmus transcribed 3.5K bytes:
> 
> contact.ng0@cryptolab.net writes:
> 
> > From: ng0 <ngillmann@runbox.com>
> >
> > * gnu/packages/forth.scm (colorforth): New variable.
> > ---
> 
> The patch to change the module name is fine (although I’d move the
> copyright update to this patch).
> 
> >  gnu/packages/forth.scm | 38 ++++++++++++++++++++++++++++++++++++++
> >  1 file changed, 38 insertions(+)
> >
> > diff --git a/gnu/packages/forth.scm b/gnu/packages/forth.scm
> > index 21a0fc2de..8854a9246 100644
> > --- a/gnu/packages/forth.scm
> > +++ b/gnu/packages/forth.scm
> > @@ -21,7 +21,9 @@
> >    #:use-module ((guix licenses) #:prefix license:)
> >    #:use-module (guix packages)
> >    #:use-module (guix download)
> > +  #:use-module (guix git-download)
> >    #:use-module (guix build-system gnu)
> > +  #:use-module (gnu packages assembly)
> >    #:use-module (gnu packages m4))
> >  
> >  (define-public gforth
> > @@ -58,3 +60,39 @@ and history.  A generic virtual machine environment, vmgen, is also
> >  included.")
> >      (home-page "https://www.gnu.org/software/gforth/")
> >      (license license:gpl3+)))
> > +
> > +(define-public colorforth
> > +  (let ((commit "94aec438f1ded202681f18801b98c52dc3beee41")
> > +        (revision "1"))
> > +    (package
> > +      (name "colorforth")
> > +      (version (string-append "0.0.0-" revision "." (string-take commit 7)))
> > +      (source (origin
> > +                (method git-fetch)
> > +                (uri (git-reference
> > +                      (url "https://github.com/narke/colorForth")
> > +                      (commit commit)))
> > +                (sha256
> > +                 (base32
> > +                  "0s602k568bm6vmvpahsms77liicg38vksn59j5m8ax4h9l9ca77r"))))
> > +      (arguments
> > +       `(#:tests? #f
> > +         #:phases
> > +         (modify-phases %standard-phases
> > +           (delete 'configure) ; no configure script
> > +           (replace 'install ; There is no 'install
> 
> Please change the comment to “no install target” or similar.  “no
> 'install” is confusing because “'install” is a quoted symbol and that
> has no meaning outside of Scheme.
> 
> > +             (lambda _
> > +               (install-file "cf2012.img"
> > +                             (string-append (assoc-ref %outputs "out")
> > +                                            "/bin")))))))
> 
> Please use “outputs” instead of “%outputs”.  Is the target “bin”
> directory created during the build?
> 
> Please also make the phase end with “#t”.
> 
> > +      (native-inputs
> > +       `(("nasm" ,nasm)))
> > +      (build-system gnu-build-system)
> > +      (home-page "https://github.com/narke/colorForth")
> > +      (synopsis "Native 32-bit colorForth for PCs, Bochs and Qemu")
> > +      (description
> > +       "Native colorForth for 32-bit PCs, at least compilable on Linux
> > + and runnable on both Bochs and Qemu.  It is adapted from
> > + @url{http://sourceforge.net/projects/colorforth, colorforth}.
> > + The original colorforth is public domain software.")
> 
> Please change the description.  The first sentence fragment should be a
> full sentence.  I don’t think “32-bit PCs” should be mentioned, nor
> should compatibility with Linux be mentioned (do they mean the kernel or
> GNU?).  Also the last sentence should not be included.

Okay.

> Could you write a description that describes the package, i.e. tells
> potential users why they would want to use it?

I will try, I'm not a colorforth user myself.

> Looks like it’s written in x86 assembly.  This would be worth mentioning
> (and I think that’s what “32-bit PCs” implied).
> 
> Could you please send an updated patch?
> 
> -- 
> Ricardo
> 
> GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
> https://elephly.net
> 

-- 
PGP and more: https://people.pragmatique.xyz/ng0/

       reply	other threads:[~2017-04-15 15:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170214185339.25538-1-contact.ng0@cryptolab.net>
     [not found] ` <20170214185339.25538-2-contact.ng0@cryptolab.net>
     [not found]   ` <871suvu8yu.fsf@elephly.net>
2017-04-15 15:28     ` ng0 [this message]
2017-04-15 16:00       ` bug#25728: [PATCH 2/2] gnu: Add colorforth ng0
2017-06-18 10:59         ` [bug#25728] " Ricardo Wurmus
2017-06-18 11:59           ` ng0
2017-06-18 13:52             ` Ricardo Wurmus
2017-06-28  9:48               ` ng0
2017-07-17 20:36                 ` Ricardo Wurmus
2017-07-17 20:43                   ` Ricardo Wurmus
2017-07-17 20:46                     ` Ricardo Wurmus
2017-07-17 21:58                       ` ng0
2017-07-23  8:35                       ` ng0
2017-08-10  8:04                         ` Konstantin Tcholokachvili
2017-10-10 13:13                           ` ng0
2017-10-11 10:45                             ` bug#25728: " ng0

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=20170415152843.2vyk7uhycuny5rov@abyayala \
    --to=contact.ng0@cryptolab.net \
    --cc=25728@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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).