From: ng0 <contact.ng0@cryptolab.net>
To: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add sedsed.
Date: Tue, 31 Jan 2017 18:30:25 +0000 [thread overview]
Message-ID: <87a8a7qdz2.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170131180333.6675-2-contact.ng0@cryptolab.net>
contact.ng0@cryptolab.net writes:
> From: ng0 <contact.ng0@cryptolab.net>
>
> * gnu/packages/admin.scm (sedsed): New variable.
> ---
> gnu/packages/admin.scm | 65 +++++++++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 64 insertions(+), 1 deletion(-)
>
> diff --git a/gnu/packages/admin.scm b/gnu/packages/admin.scm
> index 96aececbb..bb69a9df1 100644
> --- a/gnu/packages/admin.scm
> +++ b/gnu/packages/admin.scm
> @@ -12,7 +12,7 @@
> ;;; Copyright © 2016, 2017 Efraim Flashner <efraim@flashner.co.il>
> ;;; Copyright © 2016 Peter Feigl <peter.feigl@nexoid.at>
> ;;; Copyright © 2016 John J. Foerch <jjfoerch@earthlink.net>
> -;;; Coypright © 2016 ng0 <ng0@we.make.ritual.n0.is>
> +;;; Coypright © 2016, 2017 ng0 <contact.ng0@cryptolab.net>
> ;;; Coypright © 2016 Tobias Geerinckx-Rice <me@tobias.gr>
> ;;; Coypright © 2016 John Darrington <jmd@gnu.org>
> ;;;
> @@ -1926,3 +1926,66 @@ in order to be able to find it.
> @item @command{sunxi-nand-image-builder}: Prepares raw NAND images.
> @end enumerate")
> (license license:gpl2+)))
> +
> +(define-public sedsed
> + (package
> + (name "sedsed")
> + (version "1.0")
> + (source
> + (origin
> + (method url-fetch)
> + (uri (string-append "https://github.com/aureliojargas/sedsed/"
> + "archive/v" version ".tar.gz"))
> + (file-name (string-append name "-" version ".tar.gz"))
> + (sha256
> + (base32
> + "0139jkqvm8ipiwfj7k69ry2f9b1ffgpk79arpz4r7w9kf6h23bnh"))))
> + (build-system python-build-system)
> + (arguments
> + `(#:tests? #f ; No tests.
> + #:python ,python-2
> + #:phases
> + (modify-phases %standard-phases
> + (add-after 'unpack 'patch-sed-in
> + (lambda _
> + (substitute* "sedsed.py"
> + (("sedbin = 'sed'")
> + (string-append "sedbin = '" (which "sed") "'")))
> + #t))
> + (delete 'build)
> + (replace 'install
> + (lambda _
> + ;; Just one file to copy around
> + (install-file "sedsed.py" (string-append
> + (assoc-ref %outputs "out")
> + "/bin"))
> + #t))
This looks wrong in indendation. I have to check the patch again,
I just copied this from repository to repository.
> + (add-after 'install 'symlink
> + ;; Create 'sedsed' symlink to "sedsed.py".
> + (lambda* (#:key outputs #:allow-other-keys)
> + (let* ((out (assoc-ref outputs "out"))
> + (bin (string-append out "/bin"))
> + (sed (string-append bin "/sedsed"))
> + (sedpy (string-append bin "/sedsed.py")))
> + (symlink sedpy sed)
> + #t))))))
> + (home-page "http://aurelio.net/projects/sedsed")
> + (synopsis "Sed sed scripts")
> + (description
> + "@code{sedsed} can debug, indent, tokenize and HTMLize your sed(1) scripts.
> +
> +In debug mode it reads your script and add extra commands to it. When
> +executed you can see the data flow between the commands, revealing all the
> +magic sed does on its internal buffers.
> +
> +In indent mode your script is reformatted with standard spacing.
> +
> +In tokenize mode you can see the elements of every command you use.
> +
> +In HTMLize mode your script is converted to a beautiful colored HTML file,
> +with all the commands and parameters identified for your viewing pleasure.
> +
> +With sedsed you can master any sed script. No more secrets, no more hidden
> +buffers.")
> + ;; Unspecified version of GPL.
> + (license license:gpl3)))
> --
> 2.11.0
>
--
ng0 -- https://www.inventati.org/patternsinthechaos/
next prev parent reply other threads:[~2017-01-31 18:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 18:03 Sedsed contact.ng0
2017-01-31 18:03 ` [PATCH] gnu: Add sedsed contact.ng0
2017-01-31 18:30 ` ng0 [this message]
2017-01-31 18:39 ` sedsed, v2 contact.ng0
2017-01-31 18:39 ` [PATCH] gnu: Add sedsed contact.ng0
2017-02-09 19:07 ` Kei Kebreau
2017-02-10 21:35 ` ng0
2017-02-11 3:00 ` Kei Kebreau
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=87a8a7qdz2.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=contact.ng0@cryptolab.net \
--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 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).