unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: John Soo <jsoo1@asu.edu>
Cc: Guix-devel <guix-devel@gnu.org>,
	Paul Garlick <pgarlick@tourbillion-technology.com>
Subject: Re: Packaging FreeCAD
Date: Sun, 10 Mar 2019 09:25:11 +0200	[thread overview]
Message-ID: <20190310072511.GB19750@macbook41> (raw)
In-Reply-To: <CAKf5CqWsj0g5+CE2u4hFEMawo_Q7pB3ogtk8oKBQgds9qFUVMw@mail.gmail.com>

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

On Sun, Mar 10, 2019 at 02:14:15AM +0000, John Soo wrote:
> Hi guix,
> 
> Just a quick update. I have little to report on freecad. I am still stuck
> packaging pyside2. I have looked over the debian packaging rules but I am
> unfamiliar with their packaging process. I did some research and it looks
> as though they are using the normal pybuild process with some alterations
> to some paths afterward.  The package completely fails to compile for me
> and I am no expert on python build tooling. Here's what I have tried so far
> and the error: https://paste.debian.net/1072533. Any help would be very
> appreciated.
> 
> Thanks,
> 
> John
> 
> On Fri, Feb 15, 2019 at 6:33 PM John Soo <jsoo1@asu.edu> wrote:
> 
> > Thanks so much Paul! This is really helpful!
> >
> > > On Feb 15, 2019, at 9:20 AM, Paul Garlick <
> > pgarlick@tourbillion-technology.com> wrote:
> > >
> > > Hi John,
> > >
> > >> I have been getting a little stuck building the pyside2 dependencies
> > >
> > > There has been an effort to package pyside2 for Debian.  This has been
> > > completed in the last six months.
> > >
> > > A good place to look for information is
> > > https://tracker.debian.org/pkg/pyside2
> > >
> > > You can browse the source code and follow the links to the 'debian'
> > > directory, which contains the files that govern the packaging process.
> > > In general for Debian packages, the 'rules' file is worth reading and
> > > the 'patches' directory has the changes to the upstream code.
> > >
> > > One element that could be important in Guix is an update of patchelf to
> > > a recent commit (see 'update-patchelf.patch' in the patches directory).
> > >
> > > Best regards,
> > >
> > > Paul.
> > >
> >

I haven't tried building it myself yet, but two things come to mind:
Try using qtbase instead of qt, it has a much smaller footprint and will
likely be requested when it's time to include the package in Guix.

You're using version 5.12.1, and in Guix we have qt 5.11.3. It's likely
the errors you're getting are because the version of Qt is different.

-- 
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:[~2019-03-10  7:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14 12:42 Packaging FreeCAD Paul Garlick
2019-01-15 23:38 ` John Soo
2019-02-14 15:18 ` John Soo
2019-02-15 17:20   ` Paul Garlick
2019-02-15 18:33     ` John Soo
2019-03-10  2:14       ` John Soo
2019-03-10  7:25         ` Efraim Flashner [this message]
2019-03-12 15:15           ` John Soo
2019-05-09 13:50             ` John Soo
2019-05-28 20:21           ` John Soo
2019-05-30 16:23             ` Paul Garlick
2019-05-30 17:23               ` John Soo
2019-05-30 23:23                 ` Paul Garlick
2019-06-18  8:27                   ` John Soo
2019-06-18 18:11                     ` Gábor Boskovits
2019-06-18 20:33                       ` John Soo
2019-06-18 21:03                     ` Paul Garlick
2019-06-19 14:12                       ` John Soo
2019-06-30  2:45                         ` John Soo
  -- strict thread matches above, loose matches on Subject: below --
2019-01-11  9:35 Paul Garlick
2019-01-11 19:42 ` John Soo
2019-01-09 16:18 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

  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=20190310072511.GB19750@macbook41 \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=jsoo1@asu.edu \
    --cc=pgarlick@tourbillion-technology.com \
    /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 public inbox

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

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).