From: jbranso@dismail.de
To: "kiasoc5" <kiasoc5@disroot.org>,
"Ethan Reece" <guix@ethanreece.com>,
guix-devel@gnu.org
Subject: Re: Packaging Typst
Date: Sat, 13 Jul 2024 13:40:24 +0000 [thread overview]
Message-ID: <f42e9e9abfd5c6ea054658c3c8cf2f6b26abb124@dismail.de> (raw)
In-Reply-To: <b280cc0d-0cd6-420f-9d8a-c749951ae58f@disroot.org>
July 11, 2024 at 9:34 PM, "kiasoc5" <kiasoc5@disroot.org> wrote:
>
> On 7/11/24 02:21, Ethan Reece wrote:
>
> >
> > Hello,
> >
> > I created a file that packages Typst and its dependencies, and I'm > trying to figure out how to contribute it to the Guix project. What I've > done to generate the file:
> >
> > * guix import -i typst-guix.scm crate --recursive
> >
> > --recursive-dev-dependencies --allow-yanked typst-cli
> >
> > * I had to run this again for pretty_assertions@0.5 for some reason
> >
> > * Marked the modules licensed as "Unicode-3.0" as license:unicode
> >
> > * Marked the modules licensed as "Apache-2.0 with LLVM-exception" as
> >
> > license:asl2.0
> >
> > * Added a snippet at the end (generated with GPT but appears to work)
> >
> > that allows me to build everything in it using "guix build -m
> >
> > typst-guix.scm" and used this to verify that everything builds
> >
> > * Bumped a few packages from rust-1.75 to rust-1.76 that were
> >
> > complaining about it
> >
> > * For the packages where tests or build failed, disabled tests or
> >
> > build for that package so that there are no errors when I run the
> >
> > guix build command
> >
> > * Added pkg-config and openssl as dependencies for rust-typst-cli-0.11
> >
> > The file has about 2500 lines worth of dependencies, and I'm a bit > confused on how I should handle that. Should I redo all of this on > "crates-io.scm" or a different file? What branch should I do this on? > Should rust-typst-cli be changed to just typst or put in a different > file as that?
> >
> > - Ethan
> >
>
> Good job getting this to work!
That is a really solid job bro! Packaging rust stuff, I've heard is really hard. So congrats! Also I would perhaps wait a few more days to see if any other experienced developer gives you some tips on where to store your dependencies. Then I would submit a patch to guix-patches@gnu.org. That way we can put your contribution in our bug tracker, and we won't lose it. The guix manual has a section for how to contribute a patch: https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html
Thanks,
Joshua
next prev parent reply other threads:[~2024-07-13 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 6:21 Packaging Typst Ethan Reece
2024-07-12 1:34 ` kiasoc5
2024-07-13 13:40 ` jbranso [this message]
2024-07-14 19:52 ` Ethan Reece
-- strict thread matches above, loose matches on Subject: below --
2023-11-02 20:21 packaging Typst Steve George
2023-11-02 20:32 ` Alexis Simon
2023-11-03 21:41 ` Alexis Simon
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=f42e9e9abfd5c6ea054658c3c8cf2f6b26abb124@dismail.de \
--to=jbranso@dismail.de \
--cc=guix-devel@gnu.org \
--cc=guix@ethanreece.com \
--cc=kiasoc5@disroot.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).