Re: wavpack update needed
On Oct 16, 2021, at 07:02, rmgls wrote: > wavpack installed in macports need to be updated to the last > available version. > wavpack emits a warning when used with tag3 for instance. > > i downloaded the latest version from the web site > it builds fine, and seems to work fine with sox. > perhaps, it would be updated in the port tree? As far as I can tell, our wavpack port is at version 5.4.0 which is the latest one available on their web site. If you do not see this version of wavpack in your MacPorts install, run "sudo port selfupdate". If you think a newer version than that is available, file an update ticket in the issue tracker or submit it as a pull request.
Re: Which setup.py to use?
On Oct 18, 2021, at 20:58, Jerry wrote: > I want to embed the plotter Veusz in a Python script. According to the Veusz > instructions, the path to Veusz should be on the Python path and one is > advised to do this in setup.py. (Python 3.8 here). There are 123 files on my > computer called setup.py and 29 of them are in /opt/local. Which one should I > use? Is there one that sits “higher” so that non-Macports Pythons can also > see it? I'm not sure I understand the question. Every python project that builds using setuptools should have its own setup.py file that says how to set it up.
Re: Contributing to macports using your own git fork in combination with using 'port self update'
On Oct 23, 2021, at 05:43, Gerben Wierda wrote: > The way I can update my ports tree using git is: > > # Updating the master of my fork from the master of the original: > > git checkout master # Go to branch master in my local clone > git pull upstream master # Update my local clone master from the > master of the remote upstream > # (overwrites my local master with > remote github/macports/master) > git reset --hard upstream/master # Resets index and working tree of > local clone/master from remote upstream > git push origin master --force# Push local clone > (~/MacPortsDev/macports-ports) master back > # to my own remote fork > (github/gctwnl/macports-ports) > # NOTE: this closes all open > pull-requests! > # username: gctwnl > # password: GitHub Token (in BitWarden) > portindex # Tell macports to use this tree and > update the macports index > > Is there a way to do selfupdate on the base system only without messing with > the ports tree, so the base system only? Or should I just run ‘port > selfupdate’ and then use the above to do it again for the ports tree? "sudo port selfupdate" updates base using rsync and updates your ports trees using whatever method is appropriate for each of them. If a ports tree is specified in sources.conf using an rsync:// URL, then it is updated with rsync. If it is specified using a file:/// URL and the directory is a git clone, it updates it using git commands. I can't tell you right now whether the commands MacPorts uses to update a git clone are equivalent to the ones you mentioned above or whether there are relevant differences. If you want to update MacPorts base only and not update any ports trees, you can use "sudo port selfupdate --no-sync".
Re: Add M1 Hypervisor Support for QEMU Port?
On Oct 20, 2021, at 22:06, Sriranga Veeraraghavan wrote: > Is there a way to add an optional variant to the QEMU Portfile that would > apply this patch? Yes, it is technically possible to do that. However, we prefer not to include and forever maintain unofficial patches. Instead, we would prefer for such patches to be submitted to the upstream developers of the software. If they include it, then MacPorts will automatically get that and any other changes when we update to the next version of the software. If upstream elects not to include a patch, then we would have to seriously consider whether it would be appropriate for us to second-guess their decision and include it in MacPorts anyway.
Re: Question about realeasing *pkg for macOS 12 on website
I don’t know about an ETA, but you do not need to wait for them to get started. Just follow the install from source instructions in the meantime. > On 26 Oct 2021, at 1:26 pm, xgfvc via macports-users > wrote: > > Hello everyone, > > Hope you’re doing well. I have a question: Do we have an ETA on *pkg file for > macOS 12 released/uploaded on the macports website? > > Kindly, > Jacob smime.p7s Description: S/MIME cryptographic signature
Question about realeasing *pkg for macOS 12 on website
Hello everyone, Hope you’re doing well. I have a question: Do we have an ETA on *pkg file for macOS 12 released/uploaded on the macports website? Kindly, Jacob
Re: Build from local source tree
> I want to try to build Gimp from the latest checkin to the gimp-2-10 branch, > which includes a backport of the Wayland fixes which seem to have also fixed > the marching ants problem. > > Given the Portfile and files, how can I specify build from my local source > tree. Sorry, I misunderstood your original goal: If you’re interested in a fix for the marching ants problem for GIMP 2.10.28, then this will be much simpler. (For some reason, I was thinking you were trying to update the GIMP 3 prerelease.) So for this case, we can indeed vet this via `gimp2-devel`, per Bill Cole’s suggestion.
