On 2019/03/30 19:58, Enric Morales wrote:
> On 2019-03-30 14:21, Stuart Henderson wrote:
> > Tweaked tar attached;
> > Still needs doing: SHARED_LIBS needs fixing to be under ports control
> > (see comments next to SHARED_LIBS). We need to be able to bump these
> > from the port if necessary.
> >
> > Maybe also: drop the quite intrusive man gz patches and just run
> > gunzip in post-install, it's a bit less efficient at build time, but
> > avoids some pain for updates.
>
> Hi Stuart,
>
> Thank you very much for your feedback and tweaks to the port files! Attached
> you'll find the progress:
>
> * I have dropped the patch to the manpages and ungzip them in post-install,
> it's cleaner as you've said.
> * The SHARED_LIBS is also now version-controlled.
> * I also am now not harcoding the versions. However I'm struggling with the
> python bindings. The problem is that when generating the packages, both the
> py and the py3 ones will have the py files. If I set the MODPY_VERSION to 3,
> then it will be the opposite: both the py3 and the py package will have the
> py3 files. I am out of ideas to avoid hardcoding the versions in the PLISTs.
>
> I can't find any other package that builds both python bindings at the same
> time. Could you please show me the way it should be done?
Ah I didn't check the file contents ... OK - we don't really have a
"how it should be done" as it's not a great fit for the Python setup in
ports. The two options that come to mind:
- just pick one version (preferably py3) and forget about the other
- have separate ports for notmuch and py-notmuch, using the normal
FLAVOR mechanism to handle py/py3 for the latter
No comments:
Post a Comment