From: Max Nikulin <manikulin@gmail.com>
To: emacs-devel@gnu.org
Subject: Debian package with GNU manuals (was: Re: [ELPA] New package c-intro-and-ref)
Date: Thu, 12 Dec 2024 10:22:45 +0700 [thread overview]
Message-ID: <vjdku8$2h3$1@ciao.gmane.io> (raw)
In-Reply-To: <E1tLEP9-0000iP-Aa@fencepost.gnu.org>
On 11/12/2024 11:32, Richard Stallman wrote:
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> > > How about if we make ALL the GNU manuals available in one place
> > > as .deb packages, for the same of people with Debian-nased distros?
>
> > At least installed to /usr/share/info, they will cause conflicts with
> > native Debian packages.
>
> Would you please flesh out that sketchy statement? For instance,
> give me an exaple of such a conflict, and what circumstances
> would cause it to occur? Which Debian packages might conflict with
> a package that contains only a GNU manual?
Am I right that you are going to put e.g. coreutils and gnupg manuals in
this package?
Perhaps it is possible to avoid installing dedicated native Debian
packages with manuals, e.g. bash-doc, emacs-common-non-dfsg and
org-mode-docs, but I would still prefer to have manual versions matching
binaries. Another issue is that Debian packages may provide .pdf and
.html file in addition to .info ones.
The main problem is that some packages contain both important tools and
manuals for them:
dpkg -L coreutils gzip gnupg findutils | grep -F .info.gz
/usr/share/info/coreutils.info.gz
/usr/share/info/gzip.info.gz
/usr/share/info/gnupg.info.gz
/usr/share/info/find-maint.info.gz
/usr/share/info/find.info.gz
So you need to use some tricks if the new GNU package would contain e.g.
/usr/share/info/coreutils.info.gz
otherwise dpkg would fail in the case of install attempt.
By the way, why additional manuals obtained from net must be namely
*installed*? Perhaps info browser may *cache* them in a temporary
directory. Of course, nothing prevent users from downloading important
manuals to a "persistent" directory.
--
P.S.
In my taste missed lines with citation attribution makes it harder to
follow the discussion.
next prev parent reply other threads:[~2024-12-12 3:22 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 12:56 Proposal: Include C Manual from RMS in Emacs git, and/or release Jeremy Bryant
2024-11-30 13:25 ` Philip Kaludercic
2024-11-30 13:38 ` Arsen Arsenović
2024-11-30 14:12 ` Eli Zaretskii
2024-11-30 18:08 ` Arsen Arsenović
2024-11-30 20:05 ` Eli Zaretskii
2024-11-30 21:09 ` [External] : " Drew Adams
2024-12-01 6:15 ` Eli Zaretskii
2024-12-02 3:00 ` Texinfo reputation (was: Re: [External] : Re: Proposal: Include C Manual from RMS in Emacs git, and/or release) Max Nikulin
2024-12-02 12:47 ` Eli Zaretskii
2024-12-03 2:51 ` Texinfo reputation Max Nikulin
2024-12-03 12:38 ` Eli Zaretskii
2024-12-03 18:51 ` Dr. Arne Babenhauserheide
2024-12-05 4:56 ` Max Nikulin
2024-12-05 7:45 ` Dr. Arne Babenhauserheide
2024-12-06 4:47 ` Richard Stallman
2024-12-01 9:53 ` Proposal: Include C Manual from RMS in Emacs git, and/or release Arsen Arsenović
2024-12-01 10:12 ` Eli Zaretskii
2024-12-01 10:54 ` Arsen Arsenović
2024-12-01 13:04 ` Johan Myréen
2024-12-04 6:09 ` Richard Stallman
2024-11-30 13:50 ` Eli Zaretskii
2024-12-01 4:02 ` Sean Whitton
2024-12-01 7:45 ` Eli Zaretskii
2024-12-01 8:36 ` Sean Whitton
2024-12-01 10:01 ` Eli Zaretskii
2024-12-01 11:13 ` Sean Whitton
2024-12-05 5:05 ` Making the GNU C Manual easier to find in Info Richard Stallman
2024-12-05 6:30 ` Eli Zaretskii
2024-12-05 7:25 ` Integration of Info manuals in programming modes; was: " Dr. Arne Babenhauserheide
2024-12-05 7:46 ` Integration of Info manuals in programming modes Eli Zaretskii
2024-12-05 8:52 ` Visuwesh
2024-12-05 9:14 ` Eli Zaretskii
2024-12-05 9:49 ` Visuwesh
2024-12-05 11:17 ` Eli Zaretskii
2024-12-05 11:28 ` Visuwesh
2024-12-05 12:01 ` Eli Zaretskii
2024-12-05 12:39 ` Visuwesh
2024-12-05 14:26 ` Eli Zaretskii
2024-12-08 8:13 ` Integration of Info manuals in programming modes, " James Thomas
2024-12-08 8:38 ` James Thomas
2024-12-08 11:34 ` Eli Zaretskii
2024-12-08 20:10 ` Björn Bidar
[not found] ` <86msh5b48w.fsf@gmx.net>
2024-12-10 1:08 ` James Thomas
[not found] ` <87zfl60wbw.fsf@>
2024-12-08 20:46 ` Eli Zaretskii
2024-12-11 4:32 ` Richard Stallman
2024-12-05 10:06 ` Stephen Berman
2024-12-05 15:07 ` Dr. Arne Babenhauserheide
2024-12-05 16:04 ` Eli Zaretskii
2024-12-09 4:58 ` Integration of Info manuals in programming modes; was: Making the GNU C Manual easier to find in Info Richard Stallman
2024-12-09 22:49 ` Dr. Arne Babenhauserheide
2024-12-11 4:35 ` Richard Stallman
2024-12-02 4:10 ` Proposal: Include C Manual from RMS in Emacs git, and/or release Richard Stallman
2024-12-02 12:57 ` Eli Zaretskii
2024-12-03 23:03 ` [ELPA] New package c-intro-and-ref -- was " Jeremy Bryant
2024-12-04 12:33 ` Eli Zaretskii
2024-12-04 22:58 ` Jeremy Bryant
2024-12-05 5:45 ` Eli Zaretskii
2024-12-07 13:30 ` Improving info-look.el for (c) -was- " Jeremy Bryant
2024-12-07 15:09 ` Eli Zaretskii
2024-12-05 5:03 ` Max Nikulin
2024-12-05 18:47 ` Philip Kaludercic
2024-12-05 19:04 ` Eli Zaretskii
2024-12-06 10:44 ` Philip Kaludercic
2024-12-06 12:10 ` Eli Zaretskii
2024-12-06 22:40 ` Philip Kaludercic
2024-12-05 19:17 ` Stefan Monnier
2024-12-05 20:35 ` chad
2024-12-06 4:57 ` Visuwesh
2024-12-06 10:42 ` Philip Kaludercic
2024-12-06 14:58 ` Max Nikulin
2024-12-06 16:30 ` Eli Zaretskii
2024-12-08 16:41 ` Max Nikulin
2024-12-08 5:15 ` Richard Stallman
2024-12-08 7:15 ` Xiyue Deng
2024-12-08 16:50 ` Max Nikulin
2024-12-11 4:32 ` Richard Stallman
2024-12-12 3:22 ` Max Nikulin [this message]
2024-12-04 20:02 ` Suhail Singh
[not found] ` <87wmgf9h70.fsf@jeremybryant.net>
2024-12-04 23:52 ` Suhail Singh
2024-12-07 13:21 ` Jeremy Bryant
2024-12-08 20:44 ` Suhail Singh
2024-12-07 4:22 ` Richard Stallman
2024-12-07 12:29 ` Jeremy Bryant
2024-12-07 14:55 ` Björn Bidar
[not found] ` <87h67fr18v.fsf@>
2024-12-10 5:38 ` Richard Stallman
2024-12-05 5:05 ` Richard Stallman
2024-12-05 6:27 ` Eli Zaretskii
2024-12-03 20:07 ` Björn Bidar
[not found] ` <87cyi8h6n8.fsf@>
2024-12-07 16:02 ` Björn Bidar
2024-12-08 5:10 ` Richard Stallman
2024-12-08 20:07 ` Björn Bidar
2024-12-09 15:11 ` Improve access to documentation in Info format (was: Proposal: Include C Manual from RMS in Emacs git, and/or release) Suhail Singh
2024-12-11 4:37 ` Richard Stallman
2024-12-11 14:13 ` Improve access to documentation in Info format Suhail Singh
[not found] ` <874j3e2b2i.fsf@>
2024-12-11 4:32 ` Proposal: Include C Manual from RMS in Emacs git, and/or release Richard Stallman
2024-12-08 23:03 ` John ff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='vjdku8$2h3$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).