Update Pandoc (just on my machine)

  • Done
  • quality assurance status badge
Details
3 participants
  • Maxim Cournoyer
  • vidak
  • zimoun
Owner
unassigned
Submitted by
vidak
Severity
normal

Debbugs page

vidak wrote 3 years ago
(address . bug-guix@gnu.org)
86cd41c161617d66ec014fc3598b85df@riseup.net
I know that there is this issue:


And it was closed because Guix wants to stay with the LTS version of
Haskell.

But I need to use some features that come in later versions of pandoc.

A few of my static site generator projects break because I need features
that come after 2.7.x, which is the version that Guix packages.

Can someone explain to me how to package the latest pandoc just on my
own computer?

Thanks.

~vidak
Maxim Cournoyer wrote 3 years ago
(address . vidak@riseup.net)(address . 50728-done@debbugs.gnu.org)
87v92rjvps.fsf@gmail.com
Hello,

vidak@riseup.net writes:

Toggle quote (17 lines)
> I know that there is this issue:
>
> http://issues.guix.gnu.org/39798
>
> And it was closed because Guix wants to stay with the LTS version of
> Haskell.
>
> But I need to use some features that come in later versions of pandoc.
>
> A few of my static site generator projects break because I need features
> that come after 2.7.x, which is the version that Guix packages.
>
> Can someone explain to me how to package the latest pandoc just on my
> own computer?
>
> Thanks.

The first step is configuring a development setup as explained in "info
'(guix)Contributing" sections.

Then you'd want to update the version and source fields with the new
version details (guix hash -rx on the checkout or guix download
https://tarball-url) to retrieve the new hash.

Then you'd summarily review the new sources for important changes such
as a change to their licensing. A Changelog or NEWS file can be helpful
to understand what has changed, if available.

Then you'd start iterating on building the new package with something
like:

$ ./pre-inst-env guix build pandoc

If it's your lucky day it'll build without any change; but if it's a
major update you might have to modify the inputs or even update them in
prior commits.

Good luck!

If you have further questions, please ask on the help-guix@gnu.org
mailing list. I'll close this bug, as this tracker should remain focus
on actual bugs rather than update/packaging requests.

Thanks,

Maxim
Closed
zimoun wrote 3 years ago
(address . 50728@debbugs.gnu.org)(name . Maxim Cournoyer)(address . maxim.cournoyer@gmail.com)(address . vidak@riseup.net)(address . 50728-done@debbugs.gnu.org)
CAJ3okZ2mP8t31Fr7OpcoTgRjyCpAqbBxFZQrqXpgWPAOvj62DA@mail.gmail.com
Hi,

In addition to Maxim's words. :-)

On Thu, 23 Sept 2021 at 14:58, Maxim Cournoyer
<maxim.cournoyer@gmail.com> wrote:

Toggle quote (3 lines)
> The first step is configuring a development setup as explained in "info
> '(guix)Contributing" sections.

You can create a variant of the current 'pandoc' package and then use
it via "--load-path" or via your own channel or directly in a manifest
file or via "guix build -f your-variant.scm". Well, (at least) 5
ways; it depends on your needs. :-)


Toggle quote (4 lines)
> If you have further questions, please ask on the help-guix@gnu.org
> mailing list. I'll close this bug, as this tracker should remain focus
> on actual bugs rather than update/packaging requests.

Please ask on hel-guix@gnu.org or guix-devel@gnu.org if you need help.

Cheers,
simon
?
Your comment

This issue is archived.

To comment on this conversation send an email to 50728@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 50728
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help