Apps from Ports and Packages for Desktop Users

For old people who have many CD-Rs received from hospitals with their X-ray and other DICOM images in it, there is graphics/alizams to view the images on FreeBSD.
Not that you can access what the images show, but it may help remember what doctors said.
Not a portrait, but you should be able to view the images of yourself.
View attachment 25050
Does it support Qt6?
Qt5 would be removed for port at some point just like Qt4 and Qt3 were, as KDE6 is already the default now.
 
If you have archivist or hoarder instincts or you fear YouTube (or some similar website) may delete a video you find outstanding, you can download it using www/yt-dlp. It works from the terminal and has a host of options (see yt-dlp()), but the most common use is quite straightforward.

Example: To download the first volume of my crumbs (crumbs 1 to 250) in video-book form (a video form invented by yours truly that, like all my inventions, is know by, literally literally, no one), which is technically a YouTube video like any other (w/o sound or pictures, though), you would do:

Bash:
yt-dlp https://www.youtube.com/watch?v=8XQxPhfeZo8

Additionally, I just found out that there exists a GUI backend (an app that let's you use yt-dlp from a graphical interface). I installed it to take a look and my impression is that it's only worthy to install it if you have very strong archivist needs. The app in question is multimedia/py-tartube. Here's a pretty screenshot:

Screenshot_20260122_211929.png
 
Don't intend to drag this off topic, but consider, emergency patient needs to be discharged, how are you going to check out his documentation?
USB keys, emails, cellphones, whatsapps, social networks, none of it is a solution. An insured patient doesn't have to have any, nor should he.

There is actually no alternative to burning CDs.
 
I find this thread a bit too unspecific.
If you started threads about specific apps for a specific task this made sense.
While sidetone already started some of those like:

Paint applications and libraries: non-viral licenses
Vectors & Diagrams: What do you use? Share examples
Which are good modern version control systems (VCS)?
XMPP/Jabber components: focus is non-viral licenses
CAD for electronics
Motif & GTK
Playing music/audio on command-line
TUI file text readers/editors: ebook, txt...
Working with Numbers on Commandline
Gecko based web browsers
Opensource communication frameworks: XMPP, SIP, AMQP, MQTT, CAP, IAX
OMEMO for XMPP on FreeBSD
Customize your mouse cursor
Colorize your BSD shell
Keyboard backlighting
Game clones and similar games
Tabletop Games
First person shooters
Adventure games: roleplaying, sandbox, interactive story; share screenshots

But just "Apps from Ports and Packages for Desktop Users"... this is going to be a very, very loooong thread, with hundreds, of not thousand of entries, completely unsorted, and not categorized, so not to find anything in it.

Better use the
FreeBSD Ports Search
to browse all ports, when searching something specific, which is not in sidetone's lists yet, which already are just a very short selection of all what there is.
 
I find this thread a bit too unspecific.
If you started threads about specific apps for a specific task this made sense.
While sidetone already started some of those like:

Paint applications and libraries: non-viral licenses
Vectors & Diagrams: What do you use? Share examples
Which are good modern version control systems (VCS)?
XMPP/Jabber components: focus is non-viral licenses
CAD for electronics
Motif & GTK
Playing music/audio on command-line
TUI file text readers/editors: ebook, txt...
Working with Numbers on Commandline
Gecko based web browsers
Opensource communication frameworks: XMPP, SIP, AMQP, MQTT, CAP, IAX
OMEMO for XMPP on FreeBSD
Customize your mouse cursor
Colorize your BSD shell
Keyboard backlighting
Game clones and similar games
Tabletop Games
First person shooters
Adventure games: roleplaying, sandbox, interactive story; share screenshots

But just "Apps from Ports and Packages for Desktop Users"... this is going to be a very, very loooong thread, with hundreds, of not thousand of entries, completely unsorted, and not categorized, so not to find anything in it.

Better use the
FreeBSD Ports Search
to browse all ports, when searching something specific, which is not in sidetone's lists yet, which already are just a very short selection of all what there is.
I do what I can. Please, go ahead and start some threads so I can learn how to do it. Thank you.
 
Please, go ahead and start some threads so I can learn how to do it.
I linked some exemplary ones above, not by me though, but exemplary.
Yes, that's work to spend on to do such things - but they are useful.
And yes, I also told sidetone they are maybe better not be posted just as threads in a forum (here they get lost eventually), but on an own website, or in a personal blog, where somebody for example may post his art.

I very barely start any thread at all by my own. Only if I have a technical question about FreeBSD I cannot answer myself by the documentation I find/have, but especially not any off-topic threads at all.
Almost everything is already in here somehow.
What IMO we don't need, are five threads about posting screenshots, seven threads showing wallpapers, four threads about favorite music, six threads about favourite movies, four threads about favorite books (just waiting for somebody opens the fifth), etc. etc. ... by feeling it's 60% off-topic threads, and each is at least double, twice, or even more times there.

As I said in another post of mine:
While any good forums need some off-topic chit-chat to keep an authentic community alive,
everybody is asked to be disciplined enough not to let the off-topic stuff become inflationary.

As anybody can see I mostly participate in off-topic threads here, which doesn't mean, that's most what I'm doing here. What I do most is read others post - mostly the technical stuff, because I wanna learn new things about FreeBSD, and not discuss some weird opinions, and attitudes about non-FreeBSD stuff I sometimes see here.
That I cannot keep my mouth shut, but often feel the urge to let some things not stay unanswered, is my very own personal issue I have to deal with all by myself. And I try.
I actually suspended myself several times from this forums. (I actually joined 2018; this is my third account here [don't worry, the others are all stone dead, no chance to be revitalized anymore, so no sock puppet danger [I'm not that low.}]) Because weird opinions especially dangerous ones against others, and pro-extreme BS are a nuisance to me.
And off-topic chit-chat is tempting, because it can be fun. But actually it's just a waste of time.

Also when I stumble over newbies want to join FreeBSD, I want to help (like many others). Even if there are already way more than enough newbie threads, almost all repeating the same stuff over and over again - it's all already in here. One just need to dig, and not open thread, after thread, and another thread on the same topic, just because one is too lazy to dig.
But answering newbie questions, or try to convince them into FreeBSD is one (my) way to contribute to the system.

However,
but I'm also aware of two things:
A internet forum is not a replacement for a real social life.
A technical internet forum is about the technical points, and not primarily for off-topic chit-chat.

And - as I said in my post I quoted above - I only can plead to think twice, before open new threads, because, as I also already said several times, almost all of the stuff is already in here somewhere.
It simply does a forum not good, if there is one new thread opened "Post you favorite music", "What movies do you watch?", "What texteditor do you use", "Show your screenshots", "What applications there are?", "Post your favorite music", "What's your favorite movie?", "What's your favorite texteditor?", "Post some screenshots.", "Which applications do you use?", "What's your favorite music?".....at some point this just became too much.
That's inflationary, which means quality is reduced, which means the useful stuff is drowned in useless garbage.
 
I am listening to music with audio/deadbeef, but I want to hear what others are using, and what are their good points.
For deadbeef, it is a rather simple GTK2 application (GTK3 option does not compile for now). I am backing up iTunes library from Windows and on FreeBSD play from them with deadbeef.

I've also been using deadbeef for ~15 years now - the major selling point IMHO is, it doesn't try to take over all your media as other "jack of all trades" audio players are doing, which often mess around with the data in your collection, e.g. by placing some custom metadata garbage or even changing modification dates of the files/folders when reading it into their database.
DeaDBeeF does just one thing: it plays your music. You add something to a playlist, and it plays it. No mocking around with your data, demanding a database or spending hours of "analyzing" your collection...
You can extend it via plugins if you want some extra functionality, but by default its just an audio player.

Sadly the port has been outdated since forever - there were several attempts to get it updated, and there's actually a fully working patch to get the port updated to the current version 1.10.0, but that PR (PR 288563) stalled again.

If a few people who are also using or are interested in using DeaDBeeF could chime in on the PR it might finally get enough attention. All parts are in place and actually I've been using version 1.10.0 for half a year now and it builds and works just as advertised.
There's version 1.10.1 incoming (changelog file was updated 3 days ago[1]), so maybe there's a chance to get this into ports right after release.

[1] https://github.com/DeaDBeeF-Player/deadbeef/commit/fbeaacacf43b2e3861e8d3039fde01a45e44ecb4
 
In my opinion, the biggest problem is the maintainer.
He's not very proactive about updates.
There has been no response to this point either.
He's a committer and it seems to me they automatically (?) inherited maintainership for quite a number of ports. Not sure if historically any abandoned port was automatically assigned to a committer that used to commit PRs for that port or if this has other reasons.
However - If you search for their handles on bugzilla, you can see they are quite busy folks. I'd never accuse any committer of being not very proactive or even lazy - I'm sure they are doing as much as they can by sacrificing their own free time for the project. The influx of new ports and the ever increasing cadence of patches and updates on many projects is just crazy - especially linux-centered projects with their "just push some code, test it later"-attitude that often barf up multiple releases (and following security fixes) per week (I've even seen 5 releases on A SINGLE DAY) are putting an insane workload on all downstream consumers, and ultimately the committers, who have to review patches, bring them up to standards or even get them working before they make it into the ports tree.

I also had some PRs vanishing into oblivion now and then. I try to give those I consider more important some regular bumps, but I also don't want to add too much to the overall noise as this isn't helping anyone. I think if there are more individuals poking at a PR it has a much better chance to get a higher priority than a single guy constantly nagging about it on the mailing list. But again: I would never accuse any committer of being careless or intentionally ignoring PRs (if some committer reads along: huge thanks for your work!)
 
automatically (?) inherited maintainership for quite a number of ports.
Which ones specifically?

He ignores this.
Code:
If you're unable to handle all just return a set of 
them to the pool and/or try to find new maintainers.
He is also sticking to QT5 and are not at all supportive of the transition to QT6.
 
It's fine that you discuss this here. All threads are open to anyone to post whatever they want, in my opinion. I just wonder, because I don't know this, if there's any kind of "authority" to which concerns about the ports may be addressed.
 
Which ones specifically?

He ignores this.
Code:
If you're unable to handle all just return a set of
them to the pool and/or try to find new maintainers.
He is also sticking to QT5 and are not at all supportive of the transition to QT6.
TBH, Qt6 is a major bloatfest and broke a lot of things. I also wasted quite some time with it and decided to just roll back the few ports that started to hard-depend on qt6 until it was halfway up to standards (i.e. actually worked).

I haven't looked through the PRs assigned to him, so I don't want to prematurely judge anyone. So far my encounters and conversations with committers were all quite positive (except maybe gnome@ - which wasn't a conversation at all as this just seems to be an alias for /dev/null).


For now I'll wait for the upcoming 1.10.1 release, try to update the patch for the port and add it to the PR - as said: if some more people will chime in there, it might get enough attention to be finally committed (either by the maintainer/committer or another committer that might stumble over the increased noise around the PR)
 
It's fine that you discuss this here. All threads are open to anyone to post whatever they want, in my opinion. I just wonder, because I don't know this, if there's any kind of "authority" to which concerns about the ports may be addressed.
I think this is handled by the portmgr team:
https://www.freebsd.org/portmgr/policies/ (section


I removed the (unnecessary and retarded) hard dependency of qt6 to wayland for my local packages. It really is extremely annoying that linux folks try to force their crap upon everyone (see latest hard-dependency on systemd for kdm). I have roughly a dozen patches on top of my local ports tree to remove wayland and pulseaudio from various ports (and guess what: they all work fine and build faster without that junk...), and I submitted some of those patches to ports (not upstream, as that's completely pointless), especially if making them an option is trivial (e.g. already offered via build flags).
Of course none of that justifies blocking long-outstanding updates to ports - in case of DeaDBeeF qt5/6 aren't even involved (it uses gtk2/3) and other unwanted things (pulseaudio) can just be turned into (default-disabled) options for the port.
 
He's a committer and it seems to me they automatically (?) inherited maintainership for quite a number of ports. Not sure if historically any abandoned port was automatically assigned to a committer that used to commit PRs for that port or if this has other reasons.
I apologize for my ignorance, but has there ever been a case in the past where this was automatically assigned?
 
Not sure when the policy was changed, but before, assignee can be a non-committer maintainers. But currently, assignees need to be committers.
I think no reassignments were done (if I recall correctly, some PRs are kept assigned to non-committer maintainers), but if trying to do reassignment automatically, the only way would be whichever of:
  • Reset assignee and keep it unassigned until someone manually assigns.
  • Assign to the committer that committed to the ports.
 
I apologize for my ignorance, but has there ever been a case in the past where this was automatically assigned?
I don't know - that's why i added the '(?)'. Given that all committers I encountered are also maintainers to *a lot* of ports (usually completeley unrelated ones as well) made me assume that there may have been some mechanism in place that automatically assigned ports without maintainers (or ports that were abandoned) to committers. I know there have been various changes to the way ports are maintained and how PRs and commits are handled. I've been a mere little maintainer myself for a few months, so I don't have insight into the history of how it all evolved (although this might be an interesting read if there is some written history available).
 
Back
Top