unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Sai Karthik <kskarthik@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: Help with packaging for fonts without a vcs repository
Date: Tue, 11 Jan 2022 16:05:18 +0200	[thread overview]
Message-ID: <Yd2OnmM6y9pci+C2@3900XT> (raw)
In-Reply-To: <3dbd87d2-6f1a-f2f7-5054-8cd116a35b41@disroot.org>

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

On Sat, Jan 08, 2022 at 02:57:15PM +0530, Sai Karthik wrote:
> 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
> 

I think the bigger problem is that they're not versioned.o

I think your best option is to either create a separate package for each
font and then a 'meta package' which pulls them all together (like xfce
does) or to add all the fonts as origins in the inputs (like
java-cisd-base in gnu/packages/java.scm) and then install them manually
in the correct directory.

-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

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

  reply	other threads:[~2022-01-11 14:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-08  9:27 Help with packaging for fonts without a vcs repository Sai Karthik
2022-01-11 14:05 ` Efraim Flashner [this message]
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=Yd2OnmM6y9pci+C2@3900XT \
    --to=efraim@flashner.co.il \
    --cc=help-guix@gnu.org \
    --cc=kskarthik@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.
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).