unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: guix-devel <guix-devel@gnu.org>
Subject: ANN: guix-import-debian
Date: Sun, 1 May 2016 20:01:03 +0200	[thread overview]
Message-ID: <5726445F.3090000@crazy-compilers.com> (raw)

Hi,

based on a former short discussion [1] I implemented a Pyhton tool which
helps generating package definitions from Debian descriptions.

Comments and enhancements are *very* welcome.

Installation:

   pip install guix-import-debian

:Homepage: https://gitlab.com/htgoebel/guix-import-debian


`guix-import-debian` reads the Debian package description and
``.debian.tar.gz`` from the debian package servers and creates a
(hopefully useful) Guix package definition. Of course, this definition
needs to be reworked to make everything fine for committing to the
Guix project.

This basically saves you some typing and collecting data. it does not
doe the remaining work for you.

Typically things to to are:

- check the source definitons
- check the inputs and native-inputs
- check the synopsis and description
- check the outputs
- test if building works as expected
- run guix lint
- and all the other

The downloaded debian file for this package can be found in $TMP (may
be changed using option ``--tempdir``), so you can easily continue
your research.



[1] https://lists.gnu.org/archive/html/guix-devel/2016-04/msg00927.html

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

             reply	other threads:[~2016-05-01 18:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-01 18:01 Hartmut Goebel [this message]
2016-05-02  8:24 ` ANN: guix-import-debian Ludovic Courtès
2016-05-02 19:50   ` Hartmut Goebel
2016-05-03 11:43     ` Ludovic Courtès

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=5726445F.3090000@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 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).