unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Asfaw@localhost, Nardos <nasfaw@iu.edu>
Cc: guix-devel@gnu.org
Subject: Re: [External] Re: New outreachy participant introduction
Date: Tue, 08 Oct 2019 07:48:24 +0100	[thread overview]
Message-ID: <87a7abag1z.fsf@cbaines.net> (raw)
In-Reply-To: <1570504991415.84097@iu.edu>

[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]


Asfaw, Nardos <nasfaw@iu.edu> writes:

> Hi Gabor,
>
> I apologize for the late reply.
>
>> How did the installation go?
>
> Based on your suggestion I was able to install it as a package manager
> on kali (I had help from the IRC chat group).

Great, good stuff :)

>> Should you have any questions, please don't hesitate to contact
>> us. We are here to help.
>
> I am going through the packaging guide
> (https://guix.gnu.org/blog/2018/a-packaging-tutorial-for-guix/).  Are
> there more documentations on packaging? starting with packaging sounds
> interesting.

That guide is a really good place to start, there's also the reference
documentation in the manual [1], and the packages already within Guix
itself. It's really useful to look at how existing packages work, to
work out how to make new ones work in a similar way.

1: https://guix.gnu.org/manual/en/html_node/package-Reference.html#package-Reference

The next challenge is finding something to package, it needs to be
something not already packaged for Guix, but ideally where most or all
of the dependencies are already packaged for Guix. If you have ideas,
let us know and we can help work out how feasible they are.

One good starting point would be an importer, there are a set of
importers included in Guix that take a package definition from somewhere
else (like the Python package index, or Rubygems) and try to generate a
Guix package definition. If you're familiar with some packages from one
of the collections with a corresponding importer, that might be a good
place to start.

Let us know how you get on,

Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]

  reply	other threads:[~2019-10-08  6:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-03 16:11 New outreachy participant introduction Asfaw, Nardos
2019-10-03 17:29 ` Christopher Baines
2019-10-03 19:18 ` Gábor Boskovits
2019-10-05  9:28   ` Gábor Boskovits
2019-10-08  3:23     ` [External] " Asfaw, Nardos
2019-10-08  6:48       ` Christopher Baines [this message]
2019-10-08 13:24         ` zimoun
2019-10-13  0:41           ` Asfaw, Nardos
2019-10-16  8:00             ` Gábor Boskovits
2019-10-16 14:16               ` Asfaw, Nardos
2019-10-19 20:33                 ` Ludovic Courtès
2019-10-24 12:51                 ` Gábor Boskovits
2019-10-04 18:50 ` Julien Lepiller

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=87a7abag1z.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=Asfaw@localhost \
    --cc=guix-devel@gnu.org \
    --cc=nasfaw@iu.edu \
    /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).