public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: search and install packages via bash?
Date: Thu, 8 Jul 2021 16:19:13 +0200	[thread overview]
Message-ID: <20210708141913.GA21966@tik.uni-stuttgart.de> (raw)
In-Reply-To: <bf14fb2b-ddf5-8618-0da3-9ea5531c5877@dronecode.org.uk>

On Thu 2021-07-08 (13:13), Jon Turney wrote:

> You could possibly build something equivalent using 'cygcheck -p' and 
> then processing it's output

This part was easy:


W10dev:/usr/local/bin: cygsearch ksh
Found 449 matches for ksh
kshisen-debuginfo-17.04.3-1 - kshisen-debuginfo: Debug info for kshisen
kshisen-debuginfo-17.08.3-1 - kshisen-debuginfo: Debug info for kshisen
kshisen-debuginfo-17.12.3-1 - kshisen-debuginfo: Debug info for kshisen
kshisen-17.04.3-1-src - kshisen-src: KDE Shisensho game (source)
kshisen-17.08.3-1-src - kshisen-src: KDE Shisensho game (source)
kshisen-17.12.3-1-src - kshisen-src: KDE Shisensho game (source)
kshisen-17.04.3-1 - kshisen: KDE Shisensho game
kshisen-17.08.3-1 - kshisen: KDE Shisensho game
kshisen-17.12.3-1 - kshisen: KDE Shisensho game
mksh-debuginfo-53a-1 - mksh-debuginfo: Debug info for mksh (installed binaries and support files)
mksh-debuginfo-54-1 - mksh-debuginfo: Debug info for mksh (installed binaries and support files)
mksh-debuginfo-56c-1 - mksh-debuginfo: Debug info for mksh
mksh-53a-1-src - mksh-src: MirBSD Korn Shell (source)
mksh-54-1-src - mksh-src: MirBSD Korn Shell (source)
mksh-56c-1-src - mksh-src: MirBSD Korn Shell (source)
mksh-53a-1 - mksh: MirBSD Korn Shell (installed binaries and support files)
mksh-54-1 - mksh: MirBSD Korn Shell (installed binaries and support files)
mksh-56c-1 - mksh: MirBSD Korn Shell


W10dev:/usr/local/bin: cat cygsearch
#!/bin/bash

prg=$(basename $)

if [ -z "$1" -o "$1" = "-h" ]; then
  echo "usage: $prg [-a] EXPRESSION"
  echo "example: $prg zsh"
  echo "see also: cygcheck, cyginstall"
  exit
fi

if [ "$1" = "-a" ]; then
  cygcheck -p "$2"
else
  cygcheck -p "$1" | grep "$1"
fi


-- 
Ullrich Horlacher              Server und Virtualisierung
Rechenzentrum TIK         
Universitaet Stuttgart         E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a                Tel:    ++49-711-68565868
70569 Stuttgart (Germany)      WWW:    http://www.tik.uni-stuttgart.de/
REF:<bf14fb2b-ddf5-8618-0da3-9ea5531c5877@dronecode.org.uk>

  parent reply	other threads:[~2021-07-08 14:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-08  8:45 Ulli Horlacher
2021-07-08 12:13 ` Jon Turney
2021-07-08 13:53   ` Ulli Horlacher
2021-07-08 14:46     ` Marco Atzeri
2021-07-08 15:02       ` Ulli Horlacher
2021-07-08 14:19   ` Ulli Horlacher [this message]
2021-07-08 21:11     ` Richard Beels
2021-07-08 21:11     ` Richard Beels
2021-07-08 21:11     ` Richard Beels
     [not found]     ` <20210708211451.0007A3888821@sourceware.org>
2021-07-10  4:14       ` Richard Beels
     [not found]     ` <20210708211539.705673AA9C30@sourceware.org>
2021-07-10 14:13       ` Adam Dinwoodie
2021-07-10 14:20         ` Eliot Moss
2021-07-08 18:28 ` Thomas Wolff

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210708141913.GA21966@tik.uni-stuttgart.de \
    --to=framstag@rus.uni-stuttgart.de \
    --cc=cygwin@cygwin.com \
    /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.
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).