SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It's all nice and good, but basically means "manual work". And whether this "manual work" means grepping through the ChangeLog for "Removed" packages and removing them line by line, or rather blacklisting something and then carefully inspecting whether the blacklist did what you expected it to do is secondary. Personally, I prefer "removing manually", because "doing something" is always easier and less error prone than "verifying" that something has been done right.
Of course it means work. It's "work" to run -current, which is why I don't. I just don't have the time to deal with the extra work involved with tracking -current.
99% of the time, it's simple enough to follow the changelog and make any adjustments to already installed SBo packages. There's been a few big changes like when PAM and vtown were merged in that will be harder to track. Also, listing the SBo tag in the blacklist won't cause any issues with removed packages, only added packages.
The *only* time having SBo in your blacklist would be an issue is when Pat adds a package to -current that exists on SBo and that package was already installed on the computer. Not all "Added." packages will be on SBo and all the ones that are on SBo won't necessarily be installed on that machine. Thus, it's totally worth it to blacklist SBo packages on -current installs to make using clean-system easier.
Doing some bash shell piping, there have been 545 new packages added (if you just search for "Added.", you'll get 844, but once you combine the testing/ packages that were merged into the main tree, it cuts out 299 duplicate package names). When you take those 545 packages and compare them against what's on SBo, there's only 156 packages that were added to Slackware with the same package name that's on SBo.
If you're interested in what new packages in -current exist on the 14.2 SBo repo (with the exact same name), here's the list:
I have a lot of SBo packages installed on my 14.2 machine (580) and only 67 of the above packages are installed on my system. If we take the 67 packages and divide it by the number of days since -current has been in development (1624), that averages out that Pat will add a package that exists on SBo that's installed on my system about once every 24 days. If I was already dealing with the extra work of -current, that little bit of extra effort almost once a month would be no big deal.
whether this "manual work" means grepping through the ChangeLog for "Removed" packages and removing them line by line, or rather blacklisting something and then carefully inspecting whether the blacklist did what you expected it to do is secondary.
Topic is done to death here, but I'll just say that you really don't need to "carefully inspect" the outcome of slackpkg, it's simple enough to be reliable. If I uncomment the "[0-9]+_SBo" in the blacklist, do an upgrade-all, and nothing shows up, then nothing has been added to Slackware that replaced an SBo package. For small updates this isn't even necessary, but for something like vtown going into the main tree, it's (to me) just a waste of time to manually examine every package. In the meantime, the blacklist helps keep SBo separate from slackpkg for normal system maintenance, which is good.
But anyway, the real problem with all this is the fact that SBo targets stable, and Slackware releases are so long apart now that you have people running -current with best effort attempts to have SBo on -current (i.e., ponce's repo, which is great btw). So to bring it back on topic, that's my request for -current: that Slackware comes back to semi-regular releases that aren't excessively long (even if they're just point releases with some library refreshes, or whatever). Thank ye!
Can include jack ? , some packages can benefit of this , and its good to have for some apps configuration audio options. ( i think this is the last good thing on multimedia to have on slackware )
My lucky test2
Can enable on ffmpeg vidstab ? , its not autodetected , we need force option.
Quote:
--enable-libvidstab
Last edited by USUARIONUEVO; 12-10-2020 at 03:35 PM.
Can enable on ffmpeg vidstab ? , its not autodetected , we need force option.
If we're talking about rebuilding ffmpeg, might I suggest using the following patch to enable autodetection for all dependencies? This would make it much easier for people to rebuild ffmpeg once optional dependencies are installed that Pat can't or won't include in a full install. It's not as pretty to look at (and it may want some formatting changes to have commands not be as wide), but it is much, much better functionality wise.
I emailed this patch to Pat about a month and a half ago, but I'm not sure if it was seen, seen and forgot, or decided against. It still has vid.stab support as optional, but autodetected because vid.stab wasn't in -current at the time. It'd be an easy fix to move it to the "Default enabled features" section.
NOTE: libebur128 is now an internal library for ffmpeg. It should not be an option in the SlackBuild anymore as if it is manually enabled, the ./configure will fail as the option doesn't exist anymore. That is reflected on the patch below.
And if ppr:kut happens to see this, I emailed you a patch for the ffmpeg on SBo to do the same thing. Hopefully this will be something you'll consider implementing.
Last edited by bassmadrigal; 12-10-2020 at 03:52 PM.
+1 for the above patch (or some version of it); I rebuild ffmpeg whenever there's an update because of some SBo additions, and this would streamline things.
for pinentry?
Slackware's support for emacs is usually very strong, and with pinentry-emacs package, working with gpg becomes smoother.
Additionally, may we have "xfce4-xkb-plugin" in the main tree? It's basically just a flag widget for the xfce panel, but I find it very useful to see which layout is currently selected, and I think, many people here are not from the US, so are likely to benefit from it too.
So after the eventual success of building -current on now in production mail web servers etc, though i;d throw it on at home on my file server, just uses samba. nfs, (works great) just as I was about to put my feet up and install minidlna and watch some stuff....
So after the eventual success of building -current on now in production mail web servers etc, though i;d throw it on at home on my file server, just uses samba. nfs, (works great) just as I was about to put my feet up and install minidlna and watch some stuff....
try posting this in the other sticky (SBo packages not building in -current).
try posting this in the other sticky (SBo packages not building in -current).
why?
That would be OT for that thread, I am using slackware -current versions of everything on that box including ffmpeg,
building minidlna is 1.3 from source code, not any slackbuild, so the error is likely ffmpeg, since I dont see any .so files yet the old box which it used to work on, did have .so files.
updated: it seems google is full of these problems dating back several years so its an issue that seemingly was never addressed, thought it might be because it too does not have "X" installed ffmpeg does complains about X11 missing, tried Erics, but he too builds against X, a friend on IRC uses a X-less opensuse box for file server,he build minidlna straight off the bat first go, I wonder of Pat has stripped stuff out of his build, being an American and all and subject to draconian copyright, where opensuse is not.
Last edited by Nobby6; 12-11-2020 at 05:30 AM.
Reason: extra info
That would be OT for that thread, I am using slackware -current versions of everything on that box including ffmpeg,
building minidlna is 1.3 from source code, not any slackbuild, so the error is likely ffmpeg, since I dont see any .so files yet the old box which it used to work on, did have .so files.
updated: it seems google is full of these problems dating back several years so its an issue that seemingly was never addressed, thought it might be because it too does not have "X" installed ffmpeg does complains about X11 missing, tried Erics, but he too builds against X, a friend on IRC uses a X-less opensuse box for file server,he build minidlna straight off the bat first go, I wonder of Pat has stripped stuff out of his build, being an American and all and subject to draconian copyright, where opensuse is not.
That would be OT for that thread, I am using slackware -current versions of everything on that box including ffmpeg,
building minidlna is 1.3 from source code, not any slackbuild, so the error is likely ffmpeg, since I dont see any .so files yet the old box which it used to work on, did have .so files.
updated: it seems google is full of these problems dating back several years so its an issue that seemingly was never addressed, thought it might be because it too does not have "X" installed ffmpeg does complains about X11 missing, tried Erics, but he too builds against X, a friend on IRC uses a X-less opensuse box for file server,he build minidlna straight off the bat first go, I wonder of Pat has stripped stuff out of his build, being an American and all and subject to draconian copyright, where opensuse is not.
If when building minidlna the build scripts assumes that this header is in a different place than where ffmpeg installs it, that's an issue with minidlna ot how you build it as alluded by USARIONUEVO, not with Slackware.
Last edited by Didier Spaier; 12-11-2020 at 05:49 AM.
That would be OT for that thread, I am using slackware -current versions of everything on that box including ffmpeg,
Your post is off-topic for THIS thread, which is meant to request for inclusion of new/improved features and bugfixes for the next Slackware release. MiniDLNA compilation issues are not that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
