profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/ryandesign/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Ryan Schmidt ryandesign Austin, TX he/him

ryandesign/createinstalliso 2

A command line script that creates an iso disk image from a macOS install application for use with virtualization software running on Mac hardware.

ryandesign/cliclick 1

a fork of Carsten Blüm's cliclick with support for Mac OS X 10.5 and later (see the "legacy" branch). cliclick is a macOS CLI tool for emulating mouse and keyboard events

ryandesign/aircrack-ng 0

WiFi security auditing tools suite

ryandesign/angband 0

A free, single-player roguelike dungeon exploration game

ryandesign/applecommander.github.io 0

AppleCommander web site.

ryandesign/ast 0

This is the AT&T Software Technology ast software download site from AT&T Research. The AT&T AST OpenSource Software Collection provides an overview and Practical Reusable UNIX Software provides a historical perspective. You can join the ast and uwin mailgroups, or monitor the mail archives. There is also an AT&T internal talk. The man page index contains most of the ast commands and library functions; command man pages are also available at runtime using the --man or --html option of any ast command.

ryandesign/autotrace 0

bitmap to vector graphics converter

ryandesign/bastools 0

An Applesoft BASIC tool library and command-line tool.

ryandesign/buildbot 0

Python-based continuous integration testing framework; your pull requests are more than welcome!

Pull request review commentmacports/macports-ports

libzzip: update to 0.13.72

 long_description    The ZZIPlib provides read access on ZIP-archives. The \                     access files being either real files or zipped files, \                     both with the same filepath. -checksums           rmd160  d401fc327138d5b997c0cd318f808f95cea1f937 \-                    sha256  c5cf1c11a6019862e5b6daea4d7c72124affe687b9637effc7ad3caf2b7b1d96 \-                    size    1132209+checksums           rmd160  20b12141e49c6332d8fd8b610d1fa4a868d9072b \+                    sha256  61a14917400dbef5eafb482ddc862f3edad86c888a73f445f82e1ab856d24b46 \+                    size    1162325 -depends_build       port:pkgconfig \-                    port:python27+set python.branch   3.9+set python.version  [join [split ${python.branch} "."] ""] -depends_lib         port:zlib+depends_build-append \+                    port:pkgconfig \+                    port:python${python.version} -set docdir ${prefix}/share/doc/${name}+depends_lib-append  port:zlib -configure.python    ${prefix}/bin/python2.7-configure.env       ac_cv_path_PAX=:+configure.args-append \+                    -DPYTHON_EXECUTABLE=${prefix}/bin/python${python.branch} \

The good idea is adding -DPYTHON_EXECUTABLE=${prefix}/bin/python${python.branch} to cmake PortGroup but I'm too lazy to do it :)

It's not clear to me that that would be a good idea. The cmake portgroup does not include the python portgroup, so python.branch would not be defined. Better leave it up to individual ports that need this to set it as they see fit.

catap

comment created time in 2 hours

Pull request review commentmacports/macports-ports

libzzip: update to 0.13.72

 long_description    The ZZIPlib provides read access on ZIP-archives. The \                     access files being either real files or zipped files, \                     both with the same filepath. -checksums           rmd160  d401fc327138d5b997c0cd318f808f95cea1f937 \-                    sha256  c5cf1c11a6019862e5b6daea4d7c72124affe687b9637effc7ad3caf2b7b1d96 \-                    size    1132209+checksums           zziplib-0.13.72.tar.gz \+                    rmd160  20b12141e49c6332d8fd8b610d1fa4a868d9072b \+                    sha256  61a14917400dbef5eafb482ddc862f3edad86c888a73f445f82e1ab856d24b46 \+                    size    1162325 -depends_build       port:pkgconfig \-                    port:python27+set python.branch   3.9+set python.version  [join [split ${python.branch} "."] ""] -depends_lib         port:zlib+depends_build-append \+                    port:pkgconfig \+                    port:python${python.version} -set docdir ${prefix}/share/doc/${name}+depends_lib-append  port:zlib -configure.python    ${prefix}/bin/python2.7-configure.env       ac_cv_path_PAX=:+depends_test-append port:unzip \+                    port:zip -post-configure {-    set builddir [glob -dir ${worksrcpath} "*apple-darwin*"]-    reinplace -E {s|-arch [a-z0-9_]+||g} \-        ${builddir}/zzip/zziplib-uninstalled.pc \-        ${builddir}/zzip/zziplib.pc-}+patch.pre_args      -p1+patchfiles          fixed-tests.patch \+                    fixed-macports-zip-unzip.patch++# this build links its own library, so => Disable RPATH+# See: https://github.com/gdraheim/zziplib/issues/121+cmake.install_rpath {}+configure.args-delete \+    -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON \+    -DCMAKE_INSTALL_RPATH="[join [option cmake.install_rpath] \;]"+configure.pre_args-delete \+    -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON \+    -DCMAKE_INSTALL_RPATH="[join [option cmake.install_rpath] \;]"

Surely the cmake 1.1 portgroup only puts these arguments into either configure.args or configure.pre_args. I would consult the portgroup's code, figure out which it is, and then -delete these values only from the variable that actually contains the values.

It's not really intended for ports to need to delete such flags added by the portgroup. I think it's been discussed elsewhere that maybe the cmake portgroup was overzealous in including such flags. A better fix might be figuring out how to safely remove them from the portgroup without impacting existing ports. Such a fix might involve introducing a new version of the portgroup and migrating ports to it over time.

catap

comment created time in 2 hours

Pull request review commentmacports/macports-ports

libzzip: update to 0.13.72

 long_description    The ZZIPlib provides read access on ZIP-archives. The \                     access files being either real files or zipped files, \                     both with the same filepath. -checksums           rmd160  d401fc327138d5b997c0cd318f808f95cea1f937 \-                    sha256  c5cf1c11a6019862e5b6daea4d7c72124affe687b9637effc7ad3caf2b7b1d96 \-                    size    1132209+checksums           zziplib-0.13.72.tar.gz \

Does this port now need more than one distfile? Assuming it doesn't (I don't see another one), it's normal not to list the distfile name in the checksums line.

catap

comment created time in 2 hours

Pull request review commentmacports/macports-ports

libzzip: update to 0.13.72

+commit 40a99a0af9c78aaf6d673dcd2086db0bd7f5f439+Author: Kirill A. Korinsky <kirill@korins.ky>+Date:   Mon Sep 20 20:22:38 2021 +0200++    support of MacPort's zip and unzip

Our project name is MacPorts, not MacPort.

catap

comment created time in 2 hours

Pull request review commentmacports/macports-ports

libzzip: update to 0.13.72

 long_description    The ZZIPlib provides read access on ZIP-archives. The \                     access files being either real files or zipped files, \                     both with the same filepath. -checksums           rmd160  d401fc327138d5b997c0cd318f808f95cea1f937 \-                    sha256  c5cf1c11a6019862e5b6daea4d7c72124affe687b9637effc7ad3caf2b7b1d96 \-                    size    1132209+checksums           zziplib-0.13.72.tar.gz \+                    rmd160  20b12141e49c6332d8fd8b610d1fa4a868d9072b \+                    sha256  61a14917400dbef5eafb482ddc862f3edad86c888a73f445f82e1ab856d24b46 \+                    size    1162325 -depends_build       port:pkgconfig \-                    port:python27+set python.branch   3.9+set python.version  [join [split ${python.branch} "."] ""] -depends_lib         port:zlib+depends_build-append \+                    port:pkgconfig \+                    port:python${python.version} -set docdir ${prefix}/share/doc/${name}+depends_lib-append  port:zlib -configure.python    ${prefix}/bin/python2.7-configure.env       ac_cv_path_PAX=:+depends_test-append port:unzip \+                    port:zip -post-configure {-    set builddir [glob -dir ${worksrcpath} "*apple-darwin*"]-    reinplace -E {s|-arch [a-z0-9_]+||g} \-        ${builddir}/zzip/zziplib-uninstalled.pc \-        ${builddir}/zzip/zziplib.pc-}+patch.pre_args      -p1+patchfiles          fixed-tests.patch \+                    fixed-macports-zip-unzip.patch++# this build links its own library, so => Disable RPATH+# See: https://github.com/gdraheim/zziplib/issues/121+cmake.install_rpath {}

It is simpler not to list a value, rather than to list an empty value.

cmake.install_rpath
catap

comment created time in 2 hours

PullRequestReviewEvent
PullRequestReviewEvent

push eventmacports/macports-ports

imgx64

commit sha 4b179e85c21b6587faeba6878906c40a3b02be7b

vips: update to 8.11.4

view details

push time in 2 hours

PR merged macports/macports-ports

vips: update to 8.11.4 type: update maintainer: open

Description

vips: update to 8.11.4

Type(s)

<!-- update (title contains ": U(u)pdate to"), submission (new Portfile) and CVE Identifiers are auto-detected, replace [ ] with [x] to select -->

  • [ ] bugfix
  • [ ] enhancement
  • [ ] security fix
Tested on

<!-- Triple-click and copy the next line and paste it into your shell. It will copy your OS and Xcode version to the clipboard. Paste it here replacing this section. sh -c 'printf "%s\n" "macOS sw_vers -productVersion sw_vers -buildVersion uname -m" "xcodebuild -version|awk '\''NR==1{x=$0}END{print x" "$NF}'\''"'|tee /dev/tty|pbcopy --> macOS 11.6 20G165 Xcode 13.0 13A233

Verification <!-- (delete not applicable items) -->

Have you

  • [x] followed our Commit Message Guidelines?
  • [x] squashed and minimized your commits?
  • [x] checked that there aren't other open pull requests for the same change?
  • [ ] referenced existing tickets on Trac with full URL? <!-- Please don't open a new Trac ticket if you are submitting a pull request. --> N/A
  • [x] checked your Portfile with port lint?
  • [ ] tried existing tests with sudo port test? N/A
  • [x] tried a full install with sudo port -vst install?
  • [x] tested basic functionality of all binary files?

<!-- Use "skip notification" (surrounded with []) to avoid notifying maintainers -->

+5 -5

1 comment

1 changed file

imgx64

pr closed time in 2 hours

Pull request review commentmacports/macports-ports

fix azure pipeline

 case "$OS_ARCH" in         ;; esac +begingroup "Removed unused certificates"+# macOC 10.14 uses curl linked against LibreSSL

Typo: macOC

catap

comment created time in 2 hours

Pull request review commentmacports/macports-ports

fix azure pipeline

 git -C ports/ checkout -qf - git -C ports/ checkout -qf "$(git -C ports/ merge-base macports/master HEAD)" ## Ignore portindex errors on common ancestor wait $curl_portindex_pid-(cd ports/ && portindex)+(cd ports/ && sudo portindex)

Why? Doesn't the script run as root already? If this change is needed/wanted, it should be made in the GitHub Actions equivalent script as well. The scripts should be kept as similar as possible; I recently spent some effort making them so and don't want to see them diverge again.

catap

comment created time in 3 hours

Pull request review commentmacports/macports-ports

fix azure pipeline

 echo "Fetching getopt..." /usr/bin/curl -fsSLO "https://distfiles.macports.org/_ci/getopt/getopt-v1.1.6.tar.bz2" & curl_getopt_pid=$! echo "Fetching MacPorts..."-/usr/bin/curl -fsSLO "https://github.com/macports/macports-ci-files/releases/download/v${MACPORTS_VERSION}/MacPorts-${OS_MAJOR}.tar.bz2" &+/usr/bin/curl -fsSLO "https://github.com/macports/macports-ports/files/7318181/MacPorts-${OS_MAJOR}.tar.bz2.gz" &

This does not seem desirable. Instead, we should upload the real .tar.bz2 file to the right place, either on distfiles.macports.org or wherever it is that the 2.7.1 files for the GitHub Actions were placed.

catap

comment created time in 3 hours

Pull request review commentmacports/macports-ports

fix azure pipeline

 case "$OS_ARCH" in         ;; esac +begingroup "Removed unused certificates"+# macOC 10.14 uses curl linked against LibreSSL+# which gave up to checking trusted root as soon as first certificate is expired

Typo: something (can't really follow the grammar of this sentence)

catap

comment created time in 2 hours

PullRequestReviewEvent
PullRequestReviewEvent

push eventmacports/macports-ports

David Hu

commit sha a3ac062b0173243b2853788ba0549d7dd6a7ab5d

curl: update to 7.79.1

view details

push time in 3 hours

PR merged macports/macports-ports

Reviewers
curl: update to 7.79.1 type: enhancement type: update maintainer: requires approval maintainer: timeout

Description

<!-- Note: it is best to make pull requests from a branch rather than from master -->

Type(s)

<!-- update (title contains ": U(u)pdate to"), submission (new Portfile) and CVE Identifiers are auto-detected, replace [ ] with [x] to select -->

  • [ ] bugfix
  • [x] enhancement
  • [ ] security fix
Tested on

<!-- Triple-click and copy the next line and paste it into your shell. It will copy your OS and Xcode version to the clipboard. Paste it here replacing this section. sh -c 'printf "%s\n" "macOS sw_vers -productVersion sw_vers -buildVersion uname -m" "xcodebuild -version|awk '\''NR==1{x=$0}END{print x" "$NF}'\''"'|tee /dev/tty|pbcopy --> macOS 12.0 21A5552a arm64 Xcode 13.0 13A5212g

Verification <!-- (delete not applicable items) -->

Have you

  • [x] followed our Commit Message Guidelines?
  • [x] squashed and minimized your commits?
  • [x] checked that there aren't other open pull requests for the same change?
  • [ ] referenced existing tickets on Trac with full URL? <!-- Please don't open a new Trac ticket if you are submitting a pull request. -->
  • [x] checked your Portfile with port lint?
  • [ ] tried existing tests with sudo port test?
  • [ ] tried a full install with sudo port -vst install?
  • [ ] tested basic functionality of all binary files?

<!-- Use "skip notification" (surrounded with []) to avoid notifying maintainers -->

+4 -4

2 comments

1 changed file

D4v1dH03

pr closed time in 3 hours

push eventmacports/macports-ports

Ryan Schmidt

commit sha 55b705f7be3874274ab8f52896438989c26ae4e3

php80: Update to 8.0.12

view details

push time in 3 hours

issue commentADTPro/adtpro

Crash to text page 2 when sending disk over audio

I was not able to transfer any disk from the Apple //e to my Mac. In addition to the previously mentioned DOS word processing data disk containing binary files, and the second DOS disk with copies of those files, I could not transfer a third recently-initialized DOS disk containing text conversions of those binary files nor a fourth recently-initialized DOS disk containing Applesoft BASIC programs. All attempts crashed ADTPro early in the transfer, sometimes after a switch to text page 2 and a click of the speaker, sometimes not. This was with my Mac and iMic USB audio interface and cables, as opposed to my friend's Mac and his USB audio interface and cables used in the original report.

I ended up transferring the data to the Mac without ADTPro, by first BLOADing each file into memory and then using the Monitor cassette output subroutine while recording that audio in Audacity on the Mac. Later I loaded each audio file into an Apple //e emulator, LOADed it into memory, BSAVEd it to a disk image, opened those binary files in the word processor within the emulator, converted each file to text format, and then used AppleCommander to get the text files off the disk image.

There ended up being nothing wrong with the original disk after all: the "file not found" errors were due to this word processor's password protection feature; the files were readable within the word processor after supplying the right password and could then be re-saved without a password, at which point I could BLOAD them and transfer them using my method.

So it remains surprising to me that ADTPro is crashing while transferring any disk from the Apple //e to the Mac. (This might never have worked for me. I don't recall trying it before.) But I never have any trouble transferring a disk in the other direction, from the Mac to the Apple //e.

ryandesign

comment created time in 9 hours

issue commentaseprite/aseprite

Is there any plan to support Apple M1 chip? When, if any, will compiling to ARM64 be supported?

Duplicate of #2451.

Since the developers of Aseprite haven't provided a binary for Apple Silicon Macs yet, you can easily compile and install Aseprite for Apple Silicon Macs by using MacPorts.

coolqingcheng

comment created time in 15 hours

issue openedopenemulator/libemulation

Extended 80 column card cannot be removed

Thanks for OpenEmulator; it's great. I love the CRT effects and disk sounds.

This seems to be a known issue since it was mentioned in the very beta IIe functionality announcement however I didn't see a bug report filed so I wanted to file one to make sure the issue is not forgotten.

There does not appear to be a way in the Apple IIe emulation to disconnect the extended 80 column card or to replace it with a regular 80 column card (or the exciting extended 80 column text/AppleColor adapter card). In the devices window, the Apple IIe Auxiliary Slot shows as "disconnected" and there are no settings, but the computer does exhibit extended 80 column card functionality. (PR#3 works to show 80 column text; double lo-res graphics work.)

created time in 5 days

push eventmacports/macports-ports

Ryan Schmidt

commit sha 5eeb427ba74c31581cf6c73c691c59819ee846eb

libpng: Use muniversal portgroup Fixes arm64/x86_64 universal build on Apple Silicon machines. Closes: https://trac.macports.org/ticket/63008 Closes: #12575

view details

push time in 5 days

PR closed macports/macports-ports

libpng: enables the build on Apple Silicon type: enhancement maintainer: requires approval maintainer: timeout

Description

libpng: enables the build on Apple Silicon Enables to build libpng as a Universal Binary, which makes it possible to create app bundles with properly working .dylibs, should fix https://trac.macports.org/ticket/63008 (inspired by kencu's solution under https://trac.macports.org/ticket/63008#comment:5)

  • added the PortGroup muniversal 1.0 into the port file

Closes: https://trac.macports.org/ticket/63008

<!-- Note: it is best to make pull requests from a branch rather than from master -->

Type(s)

<!-- update (title contains ": U(u)pdate to"), submission (new Portfile) and CVE Identifiers are auto-detected, replace [ ] with [x] to select -->

  • [ ] bugfix
  • [x] enhancement
  • [ ] security fix
Tested on

<!-- Triple-click and copy the next line and paste it into your shell. It will copy your OS and Xcode version to the clipboard. Paste it here replacing this section. sh -c 'printf "%s\n" "macOS sw_vers -productVersion sw_vers -buildVersion uname -m" "xcodebuild -version|awk '\''NR==1{x=$0}END{print x" "$NF}'\''"'|tee /dev/tty|pbcopy --> macOS 11.6 Xcode 13.0 Mac model: MacBookPro11,1

Verification <!-- (delete not applicable items) -->

Have you

  • [x] followed our Commit Message Guidelines?
  • [x] squashed and minimized your commits?
  • [x] checked that there aren't other open pull requests for the same change?
  • [x] referenced existing tickets on Trac with full URL? <!-- Please don't open a new Trac ticket if you are submitting a pull request. -->
  • [x] checked your Portfile with port lint?
  • [x] tried existing tests with sudo port test?
  • [x] tried a full install with sudo port -vst install?
  • [x] tested basic functionality of all binary files?

<!-- Use "skip notification" (surrounded with []) to avoid notifying maintainers -->

+1 -1

1 comment

1 changed file

dob205

pr closed time in 5 days

Pull request review commentmacports/macports-ports

libvirt: Add optional variant enabling QEMU support

 variant sasl description {Use Cyrus SASL for authentication} {     configure.args-replace  -Dsasl=disabled -Dsasl=enabled } +variant qemu description {Enable the QEMU virtualization driver} {+    depends_lib-append      port:qemu+    configure.args-replace  -Ddriver_qemu=disabled -Ddriver_qemu=enabled \++}
    configure.args-replace  -Ddriver_qemu=disabled -Ddriver_qemu=enabled
}
brad-x

comment created time in 5 days

PullRequestReviewEvent
PullRequestReviewEvent

pull request commentmacports/macports-ports

libvirt: update to 7.0.0

This caused the library minor versions to decrease. See https://trac.macports.org/ticket/63466. It is important to watch out for these kinds of mistakes any time a project switches from one build system to another.

phrdina

comment created time in 5 days

issue commentcc65/cc65

printf and cprintf don't implement positional arguments

I am not ranting. My time was wasted today by having cc65 not behave the way I expected, and so I filed this bug report to attempt to save others from experiencing that frustration. Everything that needed to be said has been said, but everything that needed to be done — implementing the missing feature or documenting the omission — has not, therefore the bug should remain open until that has been done.

The cc65 documentation regarding the --standard flag does not claim to explicitly name all c99 features that are offered. Instead, regarding the cc65 mode, it says:

It is like c99 mode, but additional features are enabled. Among these are "void data", non-standard keywords without the underlines, unnamed function parameters and the requirement for main() to return an int.

The word "among" means that these are some of the things offered but not all of them. cc65 documentation also states:

cc65 supports _Static_assert from C11 and C2X

Hopefully you can see how someone might therefore conclude that other newer features are also available.

You also presuppose that someone wishing to use printf 1) has read the part of the documentation that states that cc65 primarily implements c89/c90, and 2) is aware of which parts of printf were implemented in c89/c90 and which were implemented later. This was not the case.

The cc65 documentation states that it supports printf. If it does not support all features of printf, it should document what it supports and what it does not. The place where I recommend it do so is in the function documentation. For example, I was reading the function reference for cprintf. It states:

cprintf supports the same format specifiers as printf.

Under the "See also" section, there is no link to printf documentation. I took this to mean that I should consult a standard printf reference, so I looked at man printf on my computer. It describes the n$ format option for reordering arguments. If cc65 does not support all of what is documented in my printf reference, it should provide its own reference documenting what it does support.

ryandesign

comment created time in 7 days

issue commentcc65/cc65

Cannot rerun programs

I wouldn't even call it a limitation.

I would.

If you try to re-run a program by just jumping to the entry point once more on e.g. MS-DOS, Windows or Unix, it won't work too.

That may be, I don't know, but I don't consider it relevant either way. I'm talking about Apple II software.

So the problem is rather your expectation.

My expectation is valid. When you BRUN a program on an Apple II, it is loaded into memory and then run. Yes, programs could be self-modifying in memory, but it is my valid expectation that that does not happen in my programs unless I program them to do that.

I can imagine that cc65 probably does this in order to save runtime memory, and that's great, but I think it would be a good idea for cc65 to offer an option not to do this, and for it to be the default not to do this, in order to avoid surprise.

ryandesign

comment created time in 7 days

issue commentcc65/cc65

printf and cprintf don't implement positional arguments

It also tells that c99 only enables "few" features of c99

I am aware of that.

So it is clearly documented.

Hardly.

ryandesign

comment created time in 7 days