all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Catonano <catonano@gmail.com>
To: Catonano <catonano@gmail.com>, help-guix <help-guix@gnu.org>
Subject: Re: patched packages
Date: Tue, 4 Apr 2017 20:26:43 +0200	[thread overview]
Message-ID: <CAJ98PDwD6g7yi7SkyVMSAY+mEat+ao2xDcDNrj=rijH6jQO1Og@mail.gmail.com> (raw)
In-Reply-To: <20170404180737.24w3lt7us4orbxwq@abyayala>

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

2017-04-04 20:07 GMT+02:00 ng0 <contact.ng0@cryptolab.net>:

> Catonano transcribed 2.4K bytes:
> > I put some patches in gnu/packages/patches, I listed them in Makefile.in
>
> You have to list patches in "gnu/local.mk" which is used by the top
> Makefile.  Not very clear at first, I know.
>

Thanks


> Is this patch in a commit upstream, or is it something which could be
> done with the (substitute) procedure (is that the correct term?)?
>

They are upstream.
As far as I understand they have been carefully cherrypicked by the Genshi
Fedora mantainer.

Right now I'm tired, I'm not very lucid. I've been tinkering for a bunch of
hours

From the outside Genshi looks like an abandoned package. It looks like it's
not been worked on for 5 years.

Last release doesn't pass tests and doesn't build with python3

It's not like that. The stuff is scattered in several branches, tickets and
stuff.

Because of my inexperience I didn't look immediately at the Fedora package.
There, things are clear.

I wasted a lot of time on this.

Now I have some inbalanced parenses and I'm too tired to fix them. I have
to rest a bit

Thanks

[-- Attachment #2: Type: text/html, Size: 1925 bytes --]

      reply	other threads:[~2017-04-04 18:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 16:23 patched packages Catonano
2017-04-04 18:01 ` Catonano
2017-04-04 18:07 ` ng0
2017-04-04 18:26   ` Catonano [this message]

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='CAJ98PDwD6g7yi7SkyVMSAY+mEat+ao2xDcDNrj=rijH6jQO1Og@mail.gmail.com' \
    --to=catonano@gmail.com \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.