Re: macOS status

Greetings!  Also, is there anything I can do to shorten the
pathnames/filenames in the macports builds?

Take care,

Kirill A. Korinsky <[email protected]> writes:

> Greetings,
>
> On Tue, 30 Jan 2024 17:28:11 +0100,
> Camm Maguire wrote:
>>
>> I have an old mac virtualbox which I never use except at the last point
>> in gcl releases.  Nonetheless I have fired it up, and run into the
>> problem that sed cannot put newlines into the replacement text.  You
>> guys are surely past this point.  I know next to nothing about macosx
>> versions and software installations -- perhaps you could point me to a
>> hopefully painless way to upgrade this virtualbox image to the latest
>> reasonable without destroying it.
>
> The simplest way is using image that you have without any upgrade.
>
> If you install MacPorts you may use my not published port to reproduce it.
>
> The simplest way after instalation (without switching MacPorts to git) is:
>
> 1. Replace content of
>    /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/lang/gcl/Portfile
>    into
>    https://raw.githubusercontent.com/catap/macports-ports/gcl-devel/lang/gcl/Portfile
>
> 2. Move to /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/port
>
> 3. Run portindex
>
> It adds gcl-devel port which you may build as `port build gcl-devel`.
>
> Portfile contains used gitcommit at line 78 and checksum at line 82.
>
> The simplest way to update it is:
> 1. Update git commit
> 2. Run `port bump gcl-devel`
>
> If you need access to a build folder you may find one as `port work gcl-devel`,
> and output log are available as `port logfile gcl-devel`.
>
> Keep in mind that after editing Portfile the work directory will be removed.
>
> --
> wbr, Kirill
>
>
>

-- 
Camm Maguire			     		    [email protected]
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah