Search
288 results for “smxi”
-
First @Codeberg #acxi issue (silly mistake, and good issue). acxi is a specialized CLI audio processing tool that, unlike #inxi (which is made as general utility for the wider #FreeSoftware ecosystem), is intended to meet specific audio file processing needs. It makes no effort to be 'easy' or 'user friendly', although it is immensely powerful. But not for newbies. Unlike inxi, which is fully operational out of the box, acxi does nothing until configured or run with the right CLI switches.,
-
Roy's eyes catching the light in just the right way. That's a real phenomenon of cat eye optics, not a camera glitch. Easy to see why the ignorance fueled medieval churches campaigned against cats. With little success. It's a very groovy look. I don't think I've ever seen it show so clearly during day.
-
@clacke @Di4na I completely forgot about #Freexian #debianLTS. Thanks for the reminder.
The reality of course is that corporations just want the code for free.
This grows obscene when multi hundred billion dollar companies that were created and scaled up on a full free software stack don't support free software as a core expense. That's support in billions yearly.
Facebook google most major web services.
-
@jasonkoebler Apple's "Genius" support at their stores is equally silly, as #LouisRossman has repeatedly observed in his apple repair videos. The skill required to do this type of work requires far higher income than these corporatiosn would pay, thus the service they offer cannot be real except for lowest set of problems, or just saying, oh, you need a full board replacement (when a transistor has failed). #Geeksquad was never real to me, it was not possible to do what they claimed to do.
-
@getajobmike #Unit193's solution to contributing to #freesoftware was becoming a #Debian / #Ubuntu packager, which is a thankless task, which is why I try to thank him now and then.
#damentz of #Liquorix / #ZenKernel's solution was to create that kernel project and run it for over decade.
Others run distros like #antiX, and support them. #mrmazda has supported #linux desktop users for ages.
I use specific names because supporting free software is the work of individuals dedicated to it.
-
@hanno I'm not sure where you got that idea since that's exactly what they do. I talk to #unit193 the #debian #ubuntu #inxi packager all the time and that's exactly what he does. I can double check with him if you want. Arch pacman packagers certainly pull from gitt then build. AUR is just direct live build scripts pilling from git. Rpm I don't follow but assume that's what they do. Unit193 has tracker script to alert on new tagged releases. I'll ask what he does now.
-
@hanno I'm not sure where you got that idea since that's exactly what they do. I talk to #unit193 the #debian #ubuntu #inxi packager all the time and that's exactly what he does. I can double check with him if you want. Arch pacman packagers certainly pull from gitt then build. AUR is just direct live build scripts pilling from git. Rpm I don't follow but assume that's what they do. Unit193 has tracker script to alert on new tagged releases. I'll ask what he does now.
-
@hanno I'm not sure where you got that idea since that's exactly what they do. I talk to #unit193 the #debian #ubuntu #inxi packager all the time and that's exactly what he does. I can double check with him if you want. Arch pacman packagers certainly pull from gitt then build. AUR is just direct live build scripts pilling from git. Rpm I don't follow but assume that's what they do. Unit193 has tracker script to alert on new tagged releases. I'll ask what he does now.
-
@hanno I'm not sure where you got that idea since that's exactly what they do. I talk to #unit193 the #debian #ubuntu #inxi packager all the time and that's exactly what he does. I can double check with him if you want. Arch pacman packagers certainly pull from gitt then build. AUR is just direct live build scripts pilling from git. Rpm I don't follow but assume that's what they do. Unit193 has tracker script to alert on new tagged releases. I'll ask what he does now.
-
@hanno I'm not sure where you got that idea since that's exactly what they do. I talk to #unit193 the #debian #ubuntu #inxi packager all the time and that's exactly what he does. I can double check with him if you want. Arch pacman packagers certainly pull from gitt then build. AUR is just direct live build scripts pilling from git. Rpm I don't follow but assume that's what they do. Unit193 has tracker script to alert on new tagged releases. I'll ask what he does now.
-
Fixes in #pinxi, con'd
* A big one in #inxi, only didn't show up I think because most distros ship #Xwayland, #Wayland ID always failed without Xwayland because it depended on $DISPLAY, which refers to #X.org display ID, NOT wayland's. $WAYLAND_DISPLAY added, plus some other fallbacks.In a sense, this failure was the largest, but I only found it because I installed #sway and deliberately left off Xwayland to see what I'd really need to install to get stuff running.
2/
-
#inxi update: all in #pinxi now. Nothing very exciting:
* #FreeBSD changes exposed several block device failures, all revolving around not handling /dev/gpt/[device] syntax. Some of these failures are quite obvious, some not as much. Not a big userbase, but it was a good set of bug/issue reports, which is very unusual for the BSDs.
* Adding in some more matching data, gpu vendor IDs, hyprlock, nova #rust #linux #nvidia display driver project.1/
-
https://youtube.com/watch?v=Ta0imAIz31M&si=MbzRsJLXDA1Js74J an excelllent Brodie #TechOverTea interview. 2 hour long form interview with a meta kernel scheduler developer. If you havent checked out @BrodieOnLinux you might find something thaat grabs your interest.
It's not common to hear such low level discussion and I'd been interested in schedulers because I've known #damentz of #liquorix kernel project so long. And I've helped test the experimental schedulers he's used over years.
-
@RL_Dane @mjgardner @benjaminhollon
While wanting to avoid License debates, #BSDs are free to use #GPL code in core, they just have to follow the license. It's mainly OpenBSD that tries to get rid of all GPL, which gets slightly extreme at times, like their recent effort to rewrite #rysnc to get a non gpl version. #FreeBSD has so much #linux compat stuff running I doubt they can keep GPL out of core, but don't know. I really only pay attention to OpenBSD anymore. #doas > #sudo for sure though
-
... (#acxi con'd)
A few things acxi is NOT:
* a cd ripping tool. Check out #abcde, it does a good job for cli ripping tool.
* a media player
* a strong supporter of #nonfree #audio #codecs like #AAC or #MP3. It offers adequate, basic support, and that is it.The focus is always going to be on mainly #xiph.org #vorbis things like #flac, #opus, #ogg (to a lesser extent, since vorbis has moved all dev efforts to opus).
acxi will support the others enough to let you translate them to free codecs.
-
#inxi 3.3.25 goes out the door, last matching tables updates for cpu, disk vendor. Features gpu device id updates, various fixes, the new --config options, some documentation updates.
Some other #acxi stuff I used for inxi was the organization of sub categories in the changelog, which helps readability, and makes it easier to maintain and update.
In a sense, the recent acxi updates moved its code closer to inxi style, but also some stuff moved back into inxi that I found useful.
-
With with a faint pop, just missed Chinese New Year release, #acxi 3.6.00 goes out the door. Now to move on to do other things.
For those watching, #pinxi is moving very slowly towards next #inxi, but nothing pressing really calls for a release yet, but features/enhancements are slowly building up. Better intel/amd gpu IDs for example.
-
Last changelog and tiny fixes for #acxi 3.6.00, I think maybe I'll do it today, latest tomorrow. Nothing has changed with --taglist for a few days now, and changes have only been docs and a few tiny additions which don't matter, so maybe ok to consider it stable. Note it makes no real difference, all the dev stuff goes to main branch (called 'stable' for odd historical reasons) as soon as tested anyway, so it's really just about a tagged 'release' in github terms.
-
#acxi (con'd)
* Sync convert_file also used redundant code, now it's all neat and tidy, which made it easier to improve the --dry output options as well. Also, had never indicated if copy and mkdir were running in dry mode or actually happening, now shows 'Test mode:' where relevant for the entire process.
* Earlier in process, refactored OptionsHandler::verify_selections()(to make sure options have the data they need, or conflicting options aren't used), that had gotten really messy over time. -
This is turning into a major release for #acxi, as often happens, you sort of notice odd things when working on other features, but you can't do everything at once, so the brain notes that somewhere and then when the main feature is largely complete, attention can be put on the other less related issues. I'm finding a lot now that I'm going over various features, so 3.6.00 will be a pretty major update since so many features are polished/fixed, little things wrong, code sloppiness.etc.
-
I think this is a first, since the new #acxi --config option is easy to implement, and useful, I extended it to #pinxi/#inxi. This will be in next inxi, and is in present pinxi now.
Usually acxi lags somewhat behind inxi in terms of code and logic, but due to recent heavy spate of work on acxi, the pattern is reversed for the time being.
I don't know why it never struck me to just let users easily find what config file is active, and what configs it has, but there you have it.
-
I would complain about what a pain maintaining complicated help options, man page, changelog, and now the new acxi-values.txt dev doc is overall, but the reality is, I find that when I have to document, and more important, make sure docs are consistent and actually reflect what is going on, I almost always find little glitches.
Ongoing pre-release #acxi docs/feature additions is no exception to this rule, all kinds of odd little glitches found and fixed.
But doing code AND docs is a pain.
-
This will not impact any #acxi user who has set OUTPUT_TYPE already in configs, or who starts acxi with --outtput [type]. So it's just a corner case check to avoid horrible mess for any user who was using the old default of #ogg. But I've been thinking of switching to modern default for a while, but wanted to give it some time.
-
And, since this will be a major version release, #acxi is moving from the old default output type #ogg, which is largely in maintenance mode, to #opus. Added in a few features to avoid any users who had never explicitly set OUTPUT_TYPE in configs and aren't using --output option to exit if no explicit output type set for sync actions. it could be quite nasty if you updated and had used old default ogg, then ran with new opus without realizing. This was cleanest way to handle that test.
-
Polishing up and adding public docs to #acxi. That's a first, except for its man/changelog pages. Doing this helped detect some glitches in logic for --image and --replace-images and how man page described them vs how they were working. Those issues are now resolved.
This makes 3.6.00 release close, though I tend to not want to release until no changes happen for > 24 hours. But these are fixes now, docs, etc, --taglist/-L is stable, working well.
-
@ChristosArgyrop @mjgardner nothing, lol.
Number 1 requirement for #inxi is that it runs anywhere on any system back to Perl 5.008, which was based on running on old redhat servers mainly.
As I noted a few posts back, the time I accidentally introduced a post 5.010 feature to #acxi (state with assignment of array), I got an almost immediate bug report from someone running it on old os.
With this said, maybe in a few years I'll bump inxi to 5.010, to get say and state.
-
@packy @arnandegans I like 5.008, only thing I miss is say and state, #acxi is set to 5.010, and when I accidentally let a feature slip in that broke in 5.010 I got a bug report almost immediately, lol, which surprised me, some guy was using it on an old server.
To me, one of the biggest advantage of Perl over python is that it DOES NOT BREAK over time, and if you have to update a few things, they are easy to update.
I find the assumption that I want to rewrite code every few years rude.
-
@mykhaylo #inxi and #acxi, backend tools for those, and some for work. Not a lot at work, but I found it far better in production in any scenario where I had used shell + php before. inxi is an extreme practical extraction and reporting tool, and is in a sense exactly what perl was designed for. #acxi not as extreme. Core requirement for inxi in particular is to work on 15+ year old os/hardware, so you can run it on old servers. No other language has the feature stability of perl 5.
-
And I think this largely completes this phase of #acxi active development, unless we can find some more tagging arcana corner cases to torture the code with.
Probably the most revealing project I've done with #perl so far because this one exposed 3 distinct things, one almost certainly a true bug, 2 not. This confirms my feeling that this new feature in acxi was very hard, because I had to move perl into areas I hadn't pushed it to before, thus triggering the events.
...