unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: About packaging documentation
Date: Tue, 16 Mar 2021 20:27:05 +0100	[thread overview]
Message-ID: <51eadb71-592c-d024-3163-85766a1a060c@posteo.de> (raw)
In-Reply-To: <87y2eomngw.fsf@elephly.net>

Hello Ricardo!

On 3/15/21 4:43 PM, Ricardo Wurmus wrote:
> Hi Zelphir,
>
>> https://guix.gnu.org/cookbook/en/html_node/Packaging-Tutorial.html
>> is a good
>> start. It has even got cookbook in the name. Definitely the right idea to
>> complement the general documentation. I am aware of its existence.
>> Unfortunately, I could not get the basic approach of the "Hello World package"
>> working for my package, even though it is pure guile, no other library required
>> and no FFI or anything. I would have preferred not having to go through all the
>> autotools stuff, and to have this simple way working for my package. Perhaps I
>> did something slightly wrong. I do not know. Someone mentioned on the guile user
>> mailing list, that this is all that should be needed for a pure guile package.
>> Perhaps it can be updated?
> Could you share the code you’re trying to package?  Perhaps it will
> become clearer to us what you would like to see changed in the cookbook
> — and perhaps it will become clearer to you how packaging for Guix works.

Yes, I'll link it:

https://notabug.org/ZelphirKaltstahl/guile-fslib/commit/eacdbb5ee9e30413392908d9e3988e30e9411aa7
<https://notabug.org/ZelphirKaltstahl/guile-fslib/commit/eacdbb5ee9e30413392908d9e3988e30e9411aa7>

Or:

https://notabug.org/ZelphirKaltstahl/guile-fslib/src/0.2.0
<https://notabug.org/ZelphirKaltstahl/guile-fslib/src/0.2.0>

Why not the latest version? Because I have made many changes to the repository
(not so much or none to the actual code though), to make a package using guile-hall.

I don't exactly remember the error I got, but I could try that route again and
report.

Best regards,
Zelphir

-- 
repositories: https://notabug.org/ZelphirKaltstahl



  reply	other threads:[~2021-03-16 20:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 14:46 About packaging documentation Zelphir Kaltstahl
2021-03-15 15:43 ` Ricardo Wurmus
2021-03-16 19:27   ` Zelphir Kaltstahl [this message]
2021-03-16 22:03     ` Ricardo Wurmus
2021-03-17 20:43       ` Zelphir Kaltstahl
2021-04-02 11:29       ` Zelphir Kaltstahl
2021-04-02 15:33         ` Zelphir Kaltstahl
2021-04-02 21:59           ` Ricardo Wurmus
2021-04-04 13:41             ` About packaging (was: About packaging documentation) Zelphir Kaltstahl
2021-04-04 14:35               ` Ricardo Wurmus
2021-04-04 15:57                 ` Zelphir Kaltstahl
2021-04-04 14:38               ` Tobias Geerinckx-Rice
2021-04-04 15:30                 ` Zelphir Kaltstahl
2021-04-02 21:56         ` About packaging documentation Ricardo Wurmus
2021-04-04 13:59           ` Zelphir Kaltstahl

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=51eadb71-592c-d024-3163-85766a1a060c@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --cc=help-guix@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.
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).