From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id qNxjNQIvlGaf0wAAqHPOHw:P1 (envelope-from ) for ; Sun, 14 Jul 2024 20:03:15 +0000 Received: from aspmx1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0.migadu.com with LMTPS id qNxjNQIvlGaf0wAAqHPOHw (envelope-from ) for ; Sun, 14 Jul 2024 22:03:14 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=ethanreece.com header.s=fm1 header.b=vaZaBJjQ; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=M4wTiRic; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=ethanreece.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1720987394; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=McsylgaqqncZUTd6SwftL8ZT2dlUSfzvdKzj53+cP50=; b=DWDp6oBs5jeWBDbHGsdrgRXmhRb/WRQRbKdNlOpU0TesPCE5U8gD9X0sv80/IAwsQUSgoi 5Q1fFPdiTggbqbAq+4l13LCiQf7LWw89cIrR7aEo3zgaigSyWXK4MxpXrk+tyS6G3J99jG ozLnJi85BbuiAdkpamzcGR92h97WNJEy57doJCf4XXKJE1To/wyY+tdQCSH0RPiGYW6Jw2 7T71zQ6j8M4P5tIhsnxtkK40Oj5VUnfVxCMBriKCNRCKHmINVU6SXddEDminFlex7+wr4e A3MylOh7QEqi6j9O9RaerAkq/2oDNf9/T3XKE7IanNqVGJjI3e8/zDp/bs35Gg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=ethanreece.com header.s=fm1 header.b=vaZaBJjQ; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=M4wTiRic; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=ethanreece.com ARC-Seal: i=1; s=key1; d=yhetil.org; t=1720987394; a=rsa-sha256; cv=none; b=omSXIPREc5azAzhWf5RdIhNORayh2usMmLf5dqkAVkk1sN8oOClORqftDpUhK6X1ccRD+A 0E5NXrpnHzXEqUckaxs9ZHCa1S/qY/tQS/HGavk0gXpoXVwVYFc0w1vehuURMls6LD0MOk Oq2m0I0vzQyNH++HAdUMx5syeUz6oZyZ7bNqO7yTYhGx80LdXqqfNxprCiBTlf/a6lAzLJ omMU7rReErZcStrLyr/9eM9LtaSoXySRirZSDVEUg1BaElhjbfEdCCJl6+3YzUjZt28YIp EKvCbzieUx9q0SrDUJxJEs/2rOu3C1CsTyw08/gVwtVLpeq5/AchRGIAVntR8w== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 47DE66C616 for ; Sun, 14 Jul 2024 22:03:14 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sT5HQ-0006cI-Sp; Sun, 14 Jul 2024 15:53:08 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sT5HO-0006bw-VB for guix-devel@gnu.org; Sun, 14 Jul 2024 15:53:07 -0400 Received: from fout6-smtp.messagingengine.com ([103.168.172.149]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sT5HJ-0005dL-6H for guix-devel@gnu.org; Sun, 14 Jul 2024 15:53:06 -0400 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfout.nyi.internal (Postfix) with ESMTP id 9F7091381025; Sun, 14 Jul 2024 15:52:56 -0400 (EDT) Received: from imap49 ([10.202.2.99]) by compute6.internal (MEProxy); Sun, 14 Jul 2024 15:52:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ethanreece.com; h=cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1720986776; x=1721073176; bh=Mcsylgaqqn cZUTd6SwftL8ZT2dlUSfzvdKzj53+cP50=; b=vaZaBJjQidls6byYc8td7cNjbu wJ0r7TmZICs5FtiiLgj0/4lNQOWtVVzpoDoD91teNosmEuSTqIx5itngTyRRYgKk msxnuSXn7KxQ0xmdIKIhB6MF6gErsWmcqV6icEJM4dxcUCXGlvs8CguzRYcCDENY l4gIpA1qMfAMmepHvqRbC1QlE0auyr1nWdHvKRXvXjbIQsmBIm4sd8tdwnpd5pzE Vm4rt+Pnq3fz2mg2+9bI9zZ+CKS/XgG+ikQ1aOFel2dqCxrYVBkwuuM+tkbmwO+y 9mTi/DoY4JpWBq51KNR4UHJJY35wnUturF71cttFgG/WYuLZ0M63yJzH7XmA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1720986776; x=1721073176; bh=McsylgaqqncZUTd6SwftL8ZT2dlU SfzvdKzj53+cP50=; b=M4wTiRic2UnYo86a+nyP6Q1PL54ZKpaqvWH9377H4nSi VQ9P8Mb5EYIfL44BUbxpt+dW4wlx9C9u12y1Y8k842tXfWg5Kbd8VQGWu9tHL+e5 IazYBSNMX02cJsTjTW51Xpi8rynn5Ltj1s8GB/NJbNK1/yOzgdWazjzLD/SA+HYp Sf4yijUNUQt+QLGKYe4Ljph1E4gdYldQbcOrjiYkKVbb+Vkuqi7sIuokHAucoeHG mpWgymJFJX6RmJ4b7d7E+zyS4bVTvZDHZZbx5nQxA3RLPGOPTA5Caj6cmeOq9/sd rgsUIuHjbr0P35RErYnq0HrfNp9lPTWRsEhyD7U2bg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrgedtgddugeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerredtnecuhfhrohhmpedfgfhthhgrnhcutfgvvggtvgdfuceoghhuihigsegvthhh rghnrhgvvggtvgdrtghomheqnecuggftrfgrthhtvghrnhepkeevgefffefffefgtdegvd eggfejkeehvdeludevgeehudduffdtudffueekheejnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepghhuihigsegvthhhrghnrhgvvggtvgdrtg homh X-ME-Proxy: Feedback-ID: i4959463e:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 4E18915A0092; Sun, 14 Jul 2024 15:52:56 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.11.0-alpha0-568-g843fbadbe-fm-20240701.003-g843fbadb MIME-Version: 1.0 Message-Id: <272e4458-15fd-424a-ab74-4965e0e9958d@app.fastmail.com> In-Reply-To: References: <3f05414a-e2c6-4f4f-866f-8658464637f5@app.fastmail.com> Date: Sun, 14 Jul 2024 14:52:35 -0500 From: "Ethan Reece" To: kiasoc5 , guix-devel@gnu.org Subject: Re: Packaging Typst Content-Type: multipart/alternative; boundary=5e9ddf2832b942d6ba85784485c2105b Received-SPF: pass client-ip=103.168.172.149; envelope-from=guix@ethanreece.com; helo=fout6-smtp.messagingengine.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Spam-Score: -10.01 X-Migadu-Queue-Id: 47DE66C616 X-Migadu-Scanner: mx10.migadu.com X-Migadu-Spam-Score: -10.01 X-TUID: vdrlSi9hNZwJ --5e9ddf2832b942d6ba85784485c2105b Content-Type: text/plain > Do the typst tests past? Does the binary work? The typst-cli tests pass and the binary works (I am currently using it for a small project). For the typst library, the tests require typst_dev_assets which isn't packaged in crates.io or referred to in the typst crate, so I would need to point rust-typst to the GitHub version instead of the Crates version or make it modify the Crates version to load typst_dev_assets correctly, and also add rust-typst-dev-assets to Guix which would point to the typst/typst-dev-assets GitHub repo (not sure whether I should do this or just disable tests, and should this also go in crates-io.scm or a different file). > I believe there as a package manager for typst, so if typst packages will be included in guix, would be worth creating a separate file, otherwise the typst cli package could go in markup.scm. >From what I'm seeing the `typst compile` command, which generates the file, also downloads imported packages from Typst Universe but also accepts local and custom directories, so creating a separate typst.scm file would probably be good. On Thu, Jul 11, 2024, at 20:34, kiasoc5 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! > > Do the typst tests past? Does the binary work? > > I believe that all the crates that came from crates.io should go into > crates-io.scm. The typst binary package should simply be called "typst" > unless there is a need to distinguish between a cli and gui version. I > believe there as a package manager for typst, so if typst packages will > be included in guix, would be worth creating a separate file, otherwise > the typst cli package could go in markup.scm. I'll let more experienced > members confirm or deny these assertions. > --5e9ddf2832b942d6ba85784485c2105b Content-Type: text/html Content-Transfer-Encoding: quoted-printable
Do the typst tests past? Does the binary work?

The typst-cli tests pass and the binary work= s (I am currently using it for a small project). For the typst library, = the tests require typst_dev_assets which isn't packaged in crates.io or = referred to in the typst crate, so I would need to point rust-typst to t= he GitHub version instead of the Crates version or make it modify the Cr= ates version to load typst_dev_assets correctly, and also add rust-typst= -dev-assets to Guix which would point to the typst/typst-dev-assets GitH= ub repo (not sure whether I should do this or just disable tests, and sh= ould this also go in crates-io.scm or a different file).
<= br>
I believe there as a packag= e manager for typst, so if typst packages will be included in guix,= would be worth creating a separate file, otherwise the typst cli p= ackage could go in markup.scm.

>From what I'm seeing the `typst compile` command, which generates the f= ile, also downloads imported packages from Typst Universe but also accep= ts local and custom directories, so creating a separate typst.scm file w= ould probably be good.

On Thu, Jul 11, 2024= , at 20:34, kiasoc5 wrote:
On 7/11/24 02:21, Ethan Reece wrote:
> = Hello,
> 
> I created a file that= packages Typst and its dependencies, and I'm 
> t= rying to figure out how to contribute it to the Guix project. What I've&= nbsp;
> done to generate the file:
>&n= bsp;
>   * guix import -i typst-guix.scm crat= e --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 l= icensed as "Apache-2.0 with LLVM-exception" as
> &= nbsp;   license:asl2.0
>   * Added = a snippet at the end (generated with GPT but appears to work)
<= div>>     that allows me to build everything in i= t using "guix build -m
>     typst-= guix.scm" and used this to verify that everything builds
&= gt;   * Bumped a few packages from rust-1.75 to rust-1.76 that= were
>     complaining about it
>   * For the packages where tests or build fai= led, disabled tests or
>     build = for that package so that there are no errors when I run the
>     guix build command
>&nbs= p;  * Added pkg-config and openssl as dependencies for rust-typst-c= li-0.11
> 
> The file has about 2= 500 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 sho= uld I do this on? 
> Should rust-typst-cli be chan= ged to just typst or put in a different 
> file as= that?
> 
> - Ethan

Good job getting this to work!

<= div>Do the typst tests past? Does the binary work?

I believe that all the crates that came from crates.io should go= into 
crates-io.scm. The typst binary package should= simply be called "typst" 
unless there is a need to = distinguish between a cli and gui version. I 
believe= there as a package manager for typst, so if typst packages will 
be included in guix, would be worth creating a separate fil= e, otherwise 
the typst cli package could go in marku= p.scm. I'll let more experienced 
members confirm or = deny these assertions.


--5e9ddf2832b942d6ba85784485c2105b--