all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Soo <jsoo1@asu.edu>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Packaging for guix
Date: Thu, 28 Mar 2019 13:46:16 +0000	[thread overview]
Message-ID: <CAKf5CqU5r6O1DuCdNYqauTQTPR1bm1cxt5Smy9xHkWvOW5b8_w@mail.gmail.com> (raw)
In-Reply-To: <8736n72s6u.fsf@elephly.net>


[-- Attachment #1.1: Type: text/plain, Size: 1812 bytes --]

Hi Ricardo,

Thanks.  I've been hacking in my channel and master usually has my current
work: https://github.com/jsoo1/guix-channel/blob/master/python-pyside.scm -
current commit is 59f6da3.
<https://github.com/jsoo1/guix-channel/commit/59f6da338ceab793be5c81407e46cd03424b8ae7>
Aside
- I would like to patch most of the working and compatible packages in the
channel back into guix, but freecad has been taking all my guix hacking
time.  I've attached the build log since there are some errors building
both the apiextractor package and the shiboken library.  Note that
python-pyside.scm includes work on version 1 of the Shiboken library. That
build seemed ok but freecad is moving to pyside2.  I followed nix's
strategy of building the packages separately and using cmake-build-system
instead of python (
https://github.com/NixOS/nixpkgs/blob/2d656a9729739e8ca5486058a76669d0ea4442df/pkgs/development/python-modules/pyside/shiboken.nix#L33)
for version 1. Pyside 2 is bundled into a single repository so I am not
sure I can do the same thing for it. Thanks again!

- John



On Thu, Mar 28, 2019 at 10:46 AM Ricardo Wurmus <rekado@elephly.net> wrote:

> [- pyside]
>
> Hi John,
>
> > I’ve tried using the provided python build process but I get several
> > build errors, let alone runtime issues. Would anyone be able to point
> > me in a direction to patch pyside for such a packaging system?
> > Currently I’m stuck building Shiboken. I’d particularly like guidance
> > on how to setup cmake to build it correctly (mostly the ability to
> > provide our particular flags and variables). Any help would be greatly
> > appreciated.
>
> Could you show us the package definition you have so far?  Can you also
> show us what errors you get?
>
> --
> Ricardo
>
>

[-- Attachment #1.2: Type: text/html, Size: 2585 bytes --]

[-- Attachment #2: p52jx2x4c7s2ybx4mj4gv8m97mnaxr-python-pyside-2-v5.11.3-1.4018787.drv.bz2 --]
[-- Type: application/octet-stream, Size: 34177 bytes --]

  reply	other threads:[~2019-03-28 13:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28  5:21 Packaging for guix John Soo
2019-03-28 10:45 ` Ricardo Wurmus
2019-03-28 13:46   ` John Soo [this message]
2019-04-10  9:47 ` Cristián Maureira-Fredes
2019-04-19 13:06   ` John Soo
2019-04-27 15:31     ` John Soo
2019-05-03 16:43       ` John Soo

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=CAKf5CqU5r6O1DuCdNYqauTQTPR1bm1cxt5Smy9xHkWvOW5b8_w@mail.gmail.com \
    --to=jsoo1@asu.edu \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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.