Skip to content

Instantly share code, notes, and snippets.

@dlangille

dlangille/Makefile Secret

Created May 11, 2021 20:06
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save dlangille/78902092fd8839bc4514492f949bad16 to your computer and use it in GitHub Desktop.
Save dlangille/78902092fd8839bc4514492f949bad16 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
distinfo
TIMESTAMP = 1619698508
SHA256 (lief-0.11.4.zip) = 2e33789c16b525991c8dc62a4265afdb7003e28b29744251526e3604f40ef3d4
SIZE (lief-0.11.4.zip) = 15698696
Raw
Makefile
PORTNAME= lief
DISTVERSION= 0.11.4
CATEGORIES= vrt devel
MASTER_SITES= CHEESESHOP
PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
EXTRACT_SUFX= .zip
MAINTAINER= dvl@FreeBSD.org
COMMENT= modify and abstract ELF, PE and MachO formats.
LICENSE= APACHE20
LICENSE_FILE= ${WRKSRC}/LICENSE
BUILD_DEPENDS= cmake>0:devel/cmake
USES= python
USE_PYTHON= autoplist distutils
.include <bsd.port.mk>
Raw
pkg-descr
Ics.py is a pythonic and easy iCalendar library.
Its goals are to read and write ics data in a developer friendly way.
iCalendar is a widely-used and useful format but not user friendly.
WWW: https://github.com/ics-py/ics-py
@dlangille
Copy link
Author

I'm sorry, I don't know enough to answer that information.

I'm attempting to package lief.

The process relies heavily upon the setup.py file provided in the tarball for what to package. If that does not answer your question, I can pull in someone who knows more about the Python packaging process.

@romainthomas
Copy link

Sorry I'm quite noob with FreeBSD.

So far, I used to package python projects like this:

  • python ./setup.py install (tested on FreeBSD 13)
  • pip install [--user] lief (I didn't compiled wheels for FreeBSD but I could do it)

Let's me know you thoughts regarding the way you tried to package it.

@dlangille
Copy link
Author

I had a more experienced FreeBSD Python packager look at this. They said:

  • i wouldnt be surprised if cmake is part of this issue, how/when is it ivoked? usually properly packaged pypi packages dont need cmake, and only setuptools
  • i wouldnt be using cmake at all
  • it looks like they invoke cmake directly, which then runs the setuptools bits
  • this is weird.
  • they should use cmake @ dev time, to produce the sdist, that is already processed and the resulting sdist uploaded
  • remove the cmake, and just use distutils autoplist
  • let us know how the behaviour changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment