Transferring Port Across Systems

Anthony M. Agelastos iqgrande at gmail.com
Mon Jan 13 16:55:32 UTC 2025


On 1/13/25 9:31 AM, Ryan Carsten Schmidt wrote:
> On Jan 13, 2025, at 08:42, Anthony M. Agelastos wrote:
>>
>> There are some Ports I'm able to build on System A that I cannot on 
>> System B.
>>
>
> Are there tickets for these problems?
Yes, I have opened up tickets for these. An example of one is librsvg 
#68698 <https://trac.macports.org/ticket/68698>. For this example, it 
seems there are some proxy/SSL issues preventing that build (but other 
Cargo builds seem to work fine). I am not strong enough in proxy/SSL 
stuff and Cargo to take it any further than I have in that issue. In 
that example, I have access to a system that doesn't need to use the 
proxy (where librsvg builds just fine). Other times this is ameliorated 
when it is pre-built and the *.tbz2 file is downloaded from MacPorts, 
however many of the ports don't seem to have such a build for arm64 on 
Sequoia yet.
>
>> I would like to transfer the build from A to B.
>>
>
> I don't think there are official instructions for how to do that 
> because it's not a procedure users are expected to need to do. You 
> should just be able to "sudo port install" the port on the other 
> system and if you can't then that's a bug we'd want to fix.
In general I agree. However, for weird corner cases such as my example 
above, it would be nice to be able to get a system operational (e.g., 
librsvg blocks quite a few ports) while the better fix is on the way.
>>
>> All of the instructions I found online for creating a "*.tbz2" bundle 
>> seem to only work if the Port hasn't been installed already, i.e., I 
>> couldn't find instructions on how to create it from an already built 
>> Port.
>>
>
> Perhaps because until very recently MacPorts installed the tbz2 files 
> when you installed a port.

That seems logical.

Overall, though, are my steps "correct" for what I want to do or is 
there a better way? Thank you for your help with this.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20250113/ebdda872/attachment.htm>


More information about the macports-users mailing list