Re: Portfile for osxphotos

[Kirill A. Korinsky]

Hello,

I've used osxphotos once or twice and willing to make a port file and take care 
of it.

PR will be made tonight.

--
wbr, Kirill

> On 7. Sep 2023, at 08:03, Nils Breunese  wrote:
> 
> Hello,
> 
> I recently wanted to export some photos from Apple’s Photos application and 
> import them on my partner’s Mac, without losing any metadata, keeping Live 
> Photos as-is (not just a JOG), etc. I found osxphotos [0] to be a great tool 
> for this (and it can do much more!).
> 
> The osxphotos installation instructions [1] recommend installing pipx via 
> Homebrew, and then using pipx to install osxphotos. Alternative 
> recommendations are using pip instead of pipx, or installing from source.
> 
> I could use MacPorts instead of Homebrew to install pipx, but I prefer to 
> avoid installing software via language-specific package managers, because I 
> don’t want to have to deal with all those individual package managers (pip, 
> pipx, npm, etc.), separately from MacPorts.
> 
> The osxphotos author is a MacPorts user too, but isn’t familiar with creating 
> Portfiles and currently doesn’t have time to learn how to set this up [2].
> 
> Sadly I am not familiar enough with the Python world to know how to create a 
> Portfile for osxphotos. Does someone here think MacPorts could install 
> osxphotos without using an intermediary package manager like pipx? If someone 
> would be willing to create an initial Portfile for osxphotos I wouldn’t mind 
> volunteering to keep it up to date. Let me know if you’d like to help out 
> with getting this going.
> 
> Nils.
> 
> [0] https://github.com/RhetTbull/osxphotos 
> 
> [1] https://github.com/RhetTbull/osxphotos#installation 
> 
> [2] 
> https://github.com/RhetTbull/osxphotos/issues/1199#issuecomment-1709435930 
> 


signature.asc
Description: Message signed with OpenPGP

Blacklist for architectures?

[Jason Liu]

Hi all,

Is there some sort of equivalent to 'compiler.blacklist' for supported
archs? In other words, is there some way for us to remove a selection from
the default list of 'supported_archs', rather than manually listing what is
essentially a whitelist in 'supported_archs'? Or would I use vanilla Tcl
and something like 'lsearch' or 'lremove' to remove it from the default
list?

-- 
Jason Liu

Re: [MacPorts] #68136: cross-platform portfiles and shlib extension

[René J . V . Bertin]

> Why would a port need that? It would be up to the build system to know how
> to build libraries for each platform.

Who said anything about the build systems? Have a look at the path-style 
depspecs used in many ports!

Re: Regarding github CI

[Joshua Root]

I have wanted to add some testing to the CI and buildbot for some time, 
but there are a few complications to consider. The first and simplest 
barrier is that the current release of MacPorts errors out if you try to 
run tests on a port that doesn't explicitly enable them. Related to that 
is the fact that many (most?) ports don't have any meaningful tests to run.


There are unreleased changes that start to address this. I've added one 
basic test that can be run for all ports, which at the moment just 
checks if they are using `supported_archs noarch` appropriately. More 
similarly simple and generic tests can be added, e.g. checking binaries 
for broken linking. Ports that don't set `test.run yes` will run only 
the built-in tests, while those that do will also run their custom tests 
as defined in the Portfile.


The other problem is that some projects have, shall we say, 
comprehensive test suites. This is undoubtedly a good thing for those 
projects! But as a distro building thousands of ports, we have to have a 
relatively tight limit on how long tests can take to run. There's 
currently no way of differentiating a CI-appropriate test phase from an 
unreasonably long-running one. Ideally we might have the option of 
defining a short test phase that is run on CI, and a longer one that can 
be run locally by maintainers and other interested parties if desired.


- Josh

Re: Portfile for osxphotos

[Joshua Root]

On 7/9/2023 16:03, Nils Breunese wrote:
Does someone here think MacPorts could 
install osxphotos without using an intermediary package manager like 
pipx? 


Yes, it looks like it's a standard setuptools build system, so the 
python portgroup should handle it fine. The bigger job might be adding 
ports for any dependencies that we don't currently have. I do see a lot 
of version pinning in the dependency list, which is something we don't 
support well, but it's also often unneeded.


That said, it might be worth taking a moment to consider what value 
installation via MacPorts adds, compared to creating a venv and 
installing osxphotos into it with pip. Typically we add python modules 
to MacPorts because either something else in MacPorts needs them, or 
they have dependencies that pip can't install.


If someone would be willing to create an initial Portfile for 
osxphotos I wouldn’t mind volunteering to keep it up to date. Let me 
know if you’d like to help out with getting this going.


Here's an incomplete and untested first pass at one, based on a template 
from the portfile-gen script: 



- Josh

Portfile for osxphotos

[Nils Breunese]

Hello,

I recently wanted to export some photos from Apple’s Photos application and 
import them on my partner’s Mac, without losing any metadata, keeping Live 
Photos as-is (not just a JOG), etc. I found osxphotos [0] to be a great tool 
for this (and it can do much more!).

The osxphotos installation instructions [1] recommend installing pipx via 
Homebrew, and then using pipx to install osxphotos. Alternative recommendations 
are using pip instead of pipx, or installing from source.

I could use MacPorts instead of Homebrew to install pipx, but I prefer to avoid 
installing software via language-specific package managers, because I don’t 
want to have to deal with all those individual package managers (pip, pipx, 
npm, etc.), separately from MacPorts.

The osxphotos author is a MacPorts user too, but isn’t familiar with creating 
Portfiles and currently doesn’t have time to learn how to set this up [2].

Sadly I am not familiar enough with the Python world to know how to create a 
Portfile for osxphotos. Does someone here think MacPorts could install 
osxphotos without using an intermediary package manager like pipx? If someone 
would be willing to create an initial Portfile for osxphotos I wouldn’t mind 
volunteering to keep it up to date. Let me know if you’d like to help out with 
getting this going.

Nils.

[0] https://github.com/RhetTbull/osxphotos
[1] https://github.com/RhetTbull/osxphotos#installation
[2] https://github.com/RhetTbull/osxphotos/issues/1199#issuecomment-1709435930