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.
IIRC, man-deb is the equivalent of slackware's manpages package, not man itself. man doesn't include manpages and the manpages/man-db provide some manpages which are not included with other packages.
https://wiki.debian.org/ManPage
"The man-db package includes three tools for finding information and/or documentation about your Linux system: man, apropos and whatis."
The original question "Should slackware upgrade to man-db if man is abandoned?"
Is your answer "No"?
Yes, my answer is no.
"Abandoned" only matters for a software that doesn't work anymore, have security holes or needs new features.
If PV wants to ship the man pages additional utilities[1] found in man-db he can just add them to man-pages. Actually that's not a matter of upgrading a binary, rather a packaging decision.
Also, bear in mind that the name, version number or date of release of a package do not mean much. What counts is the content of the package.
[1]mandb and catman, as zsoelim is a symlink to soelim, already shipped in groff.
Last edited by Didier Spaier; 10-24-2015 at 12:08 PM.
"Abandoned" only matters for a software that doesn't work anymore, have security holes or needs new features.
How would we know if man-1.6g has bugs or needs new features? Are you again saying you know it is flawless?
Earlier you said "As long as these programs work (and AFAIK they do)".
Do you mean as long as they work then no one should need to file bugs or ask for additional features? This is not the open source way.
How would we know if man-1.6g has bugs or needs new features? Are you again saying you know it is flawless?
Earlier you said "As long as these programs work (and AFAIK they do)".
No program is flawless. I am just saying that I am not aware of any bug report or feature request about the programs in this package.
Quote:
Do you mean as long as they work then no one should need to file bugs or ask for additional features? This is not the open source way.
The open source way for an orphaned project is that someone takes the initiative of adopting it or forking it if need be.
But let's be practical instead of rhetorical: do you, personally, have a feature request that you would like to submit to someone or found a bug? If not, I really do not see your point.
Also, how do you know that the binaries shipped in man-db are better than those in man-1.6g? Can you provide any evidence?
Last, be aware that a package and/or source tarball being hosted e.g. in a Debian or Fedora repository do not imply that they are actively maintained, unless you equate "changing the build number to fit the incoming distribution release" to "actively maintaining".
Last edited by Didier Spaier; 10-24-2015 at 12:36 PM.
No program is flawless. I am just saying that I am not aware of any bug report or feature request about the programs in this package.
How would you be aware of any? There's no place to report bugs or feature requests. Slackware is not the only distro using man-1.6g.
Quote:
The open source way for an orphaned project is that someone takes the initiative of adopting it or forking it if need be.
Is that also the slackware way? Who will host it then and where? If it's not the slackware way, then what is the slackware way? To leave things as they are?
So if I adopt man-1.6g will slackware then take any new features or bug fixes from my repo?
How would you be aware of any? There's no place to report bugs or feature requests. Slackware is not the only distro using man-1.6g.
Simple:
If there is a known upstream, go there.
Else, for all packages shipped in Slackware, this forum is the right place, at least for bug reports.
Quote:
Is that also the slackware way?
Ask PV or a Slackware contributor.
Quote:
Who will host it then and where?
Any volunteer with the needed skills. That's how open source software work.
Quote:
If it's not the slackware way, then what is the slackware way? To leave things as they are?
Again I do not speak on behalf of PV. But I am sure he can't adopt all orphaned open source projects. If you have a better idea, please share it with us.
Quote:
So if I adopt man-1.6g will slackware then take any new features or bug fixes from my repo?
How could you be "aware" of any bug reports or feature requests when there is no source repository upstream? Where are you getting your information?
As for any other software in the same situation, and there are many: coming from a security advisory, a feature or bug request posted in a forum, whatever.
This being said I am not in a mood to endlessly answer someone arguing in an aim that I do not understand.
Maybe you just would like to have man-1.6g replaced by man-db? I am not in concern then, but I think that PV is aware of this thread, so probably you do not need to elaborate further.
This being said you are free to post again in this thread. I won't.
Since there is no upstream, Didier is likely making his claim about not being aware of bugs due to the lack of reports on this forum about it. Pat is not one to jump on the latest and greatest unless there's a reason to (as Didier said, to fix bugs, add new features, etc). Just because a project might be abandoned does not mean it can't be used in Slackware. As has been discussed previously on the forum, even if a program can't be compiled, yet it runs without issue, that is not a reason to replace it.
If issues are found with an abandoned program then Pat will make a decision on what to do. That could mean switch to a different package, try to fix the current one with patches, use a forked version (if it is available), or remove the package completely without installing a replacement (not really possible with man). Any speculation on this forum is just that... speculation. We can't know what Pat would do until it occurs.
The politest word I can think of for that is "bollocks". *If* there was a known bug -- which clearly there isn't, otherwise you'd have mentioned it already --
Here
PV's email
bugtraq, full disclosure, CERT, Open Source Security, etc
or just fork it on Github and fix it
I have personally fixed wayyy over 100 SlackBuilds for -current, so I know there are *very* many projects that are abandoned and broken (even if they look maintained), and I know that many of them get fixed by distro packagers like me, or by random people who just fork & fix on github. And I can quote examples of all this, but frankly it is Saturday night and I can't be arsed.
Quote:
Originally Posted by Rinndalir
or feature requests. So if I adopt man-1.6g will slackware then take any new features or bug fixes from my repo?
If it's a useful feature -- *yes* -- obviously. Do you have an actual feature in mind for transformative disruption of manpage technology, or is this all just hypothetical moaning?
Quote:
Originally Posted by Rinndalir
How could you be "aware" of any bug reports or feature requests when there is no source repository upstream? Where are you getting your information?
The Googles (duh), Github, and distro repos. I have git etc for Debian, Fedora, Arch, Gentoo and Mageia bookmarked...
*If* there was a known bug -- which clearly there isn't, otherwise you'd have mentioned it already
This makes no sense. You are saying there's no bugs or feature requests because I didn't report one.
Quote:
[*]bugtraq, full disclosure, CERT, Open Source Security, etc
I couldn't find any of these for man-1.6g but you didn't read this entire thread and just wanted to jump in so I understand how you would answer incorrectly.
Quote:
I have personally fixed wayyy over 100 SlackBuilds for -current, so I know there are *very* many projects that are abandoned and broken (even if they look maintained), and I know that many of them get fixed by distro packagers like me
What fixes did you make? Or did you get patches? What packages?
Quote:
, or by random people who just fork & fix on github.
I never knew slackware took pull requests or used github. Please post some links to those.
Quote:
And I can quote examples of all this, but frankly it is Saturday night and I can't be arsed.
Quote:
Github, and distro repos. I have git etc for Debian, Fedora, Arch, Gentoo and Mageia bookmarked...
What about git for slackware? Can you share that bookmark? Or just share a man-1.6g bookmark?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.