unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: which ubuntu package has tput
Date: Sat, 18 Jun 2022 09:47:17 +1000	[thread overview]
Message-ID: <87mteargam.fsf@gmail.com> (raw)
In-Reply-To: <YqzdU+ohOmFerv5X@tuxteam.de>


<tomas@tuxteam.de> writes:

> [[PGP Signed Part:Undecided]]
> On Fri, Jun 17, 2022 at 10:59:08AM -0700, Jim Porter wrote:
>> On 6/17/2022 10:01 AM, hput wrote:
>> > Compiling emacs today I tried my best to find out what pkg holds
>> > tputs.
>> 
>> tput should be in ncurses-bin:
>> <https://packages.ubuntu.com/search?searchon=contents&keywords=tput&mode=exactfilename&suite=jammy&arch=any>.
>> 
>> Once you know where to look (a non-trivial matter!), it's pretty easy to
>> figure this out. Just go to <https://packages.ubuntu.com/> and enter your
>> search under "Search the contents of packages".
>
> Or install package apt-cache and do an "apt-cache search tput".
>

A 'trick' I find useful on many GNU Linux distributions is to use
whatever the package management system is to list the build dependencies
for their version of emacs. For example, on Debian based systems, you
can do something like 

apt build-dep emacs27

which will list and install all the build dependencies associated with
the emacs 27 included in that distro. when installing a newer version of
Emacs, there may be some new dependencies not included, but the above
will at least give you most of them. If you only want to build the text
version (no X), then use the no X package version. From memory, doing
this against Ubuntu's emacs27 gave me all the dependencies needed to
build either Emacs 28 or 29. 

Fedora's dnf command has builddep, which does a similar task. I'm sure
other package managers have similar. 



  reply	other threads:[~2022-06-17 23:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 17:01 which ubuntu package has tput hput
2022-06-17 17:59 ` Jim Porter
2022-06-17 20:00   ` tomas
2022-06-17 23:47     ` Tim Cross [this message]
2022-06-18  6:19 ` Eli Zaretskii
2022-06-18 15:19 ` hput

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=87mteargam.fsf@gmail.com \
    --to=theophilusx@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).