From: Sai Karthik <kskarthik@disroot.org>
To: help-guix@gnu.org
Subject: Help with packaging for fonts without a vcs repository
Date: Sat, 8 Jan 2022 14:57:15 +0530 [thread overview]
Message-ID: <3dbd87d2-6f1a-f2f7-5054-8cd116a35b41@disroot.org> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 634 bytes --]
Hello guix!
I want to package a bunch of OFL license fonts for guix called
teluguvijayam[1]. These fonts are not available on git repo. We have
packaged these fonts for debian using a shell script[2] which downloads
fonts from the source website & creates a tarball, Which is later used
in packaging.
I need help about how to approach this in guix. I am new to guix & this
would be my first packaging attempt :)
[1] https://salsa.debian.org/fonts-team/fonts-teluguvijayam
[2]
https://salsa.debian.org/fonts-team/fonts-teluguvijayam/-/blob/master/debian/create-orig-source
--
https://kskarthik.gitlab.io/
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3185 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next reply other threads:[~2022-01-09 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 9:27 Sai Karthik [this message]
2022-01-11 14:05 ` Help with packaging for fonts without a vcs repository Efraim Flashner
2022-01-11 21:28 ` Pascal Lorenz
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=3dbd87d2-6f1a-f2f7-5054-8cd116a35b41@disroot.org \
--to=kskarthik@disroot.org \
--cc=help-guix@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.
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).