On 19/2/25 21:56, Stuart Henderson wrote:
On 2025-02-19, Stuart Longland VK4MSL <m...@vk4msl.com> wrote:
Wondering if there was a Mastodon client in OpenBSD's ports tree, I did
a `make search key=mastodon` and was promptly told I need to install
`portslist` before I can do that.
net/toot if you can get python to build. (others are either too heavy
for mips64el, or tut is written in go which is not available on mips64el).
Yes, Python seems to be an issue. Specifically I saw `lang/python/2.7`
but not `lang/python/3`. (Yet, I'm sure I've installed Python 3 on
OpenBSD 7.6 via packages, so clearly it *has* been built somewhere.)
Now, it suggests I run `pkg_add portslist`, which fails because there's
no package repository.
I did a `find` to see if I could locate a "portslist" package in the
ports tree… and still no luck. `sqlports` is there, and that may be the
ultimate answer, but those docs (and the error message in ports) could
That one is indeed produced by the sqlports package;
Ahh. So it's a sub-package of the `sqlports` port.
It will take quite some time to produce (starting with building sqlite
and DBI).
Yeah, I'm used to these machines taking a while. The Cobalt Qube2 I
have is even slower (250MHz RM5231 MIPS IV with no L2 cache).
You fire the command off, walk away and cross your fingers whilst you do
something else for the next week and it grinds away. I don't miss doing
Gentoo/MIPS stage builds on that old thing, the Fuloong 2Es Gentoo
eventually had donated felt like a supercomputer in comparison.
probably use a pointer to the appropriate port name which installs
`portslist` -- for those second-class architectures where packages are
not being built.
I'd worry that people will then try to use it when they don't need to,
and if their ports tree is not particularly clean they'll run into
problems and ask questions about it without giving full information
about what they're doing, which often results in wasting a bunch
of time trying to figure out what's going on...
Fair enough, and 99% of the time, people are using an architecture where
packages are being built already… and using ports just for the bits
they're missing, so the advice works fine.
A hint that this is part of `sqlports` would steer the remaining 1% in
the right direction.
Regards,
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
