Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: gscan2pdf needs pdftk!
Date: Tue, 18 Jun 2019 02:42:55 +0200	[thread overview]
Message-ID: <20190618004255.1YcJzvvSLTimsKiJicm2uWIP7dW6lwY2zgohUXeUuoI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12517@inbox.vuxu.org>

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

New comment by misuchiru03 on void-packages repository

https://github.com/void-linux/void-packages/issues/12517#issuecomment-502901613
Comment:
I don't know if this would happen. gcc-java used to be part of the `gcc` package, but has been removed from `gcc` and will no longer be maintained; it is required for `pdftk` to be built.  You can try your hand at making a template to build yourself, or if someone is nice and get it for you, that'd be cool. But I think most will turn that down unless they have a vested interest in the product as well.

Archlinux has a few PKGBUILD templates to view in relation to pdftk:
[pdftk](https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=pdftk)
[gcc-gcj-ecj](https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=gcc-gcj-ecj) -- required by pdftk
[gcc6](https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=gcc6) -- required by pdftk and gcc-gcj-ecj

You can use the PKGBUILD as a direction to go for your template creation for these packages (package names may differ, just verify names in the void repo).

  reply	other threads:[~2019-06-18  0:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 21:57 [ISSUE] " voidlinux-github
2019-06-18  0:42 ` voidlinux-github [this message]
2019-06-18  0:59 ` voidlinux-github
2019-06-18 10:03 ` voidlinux-github
2019-06-18 10:03 ` [ISSUE] [CLOSED] " voidlinux-github

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190618004255.1YcJzvvSLTimsKiJicm2uWIP7dW6lwY2zgohUXeUuoI@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.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 NNTP newsgroup(s).