unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Hartmut Goebel <h.goebel@crazy-compilers.com>,
	Pierre Neidhardt <mail@ambrevar.xyz>,
	42291@debbugs.gnu.org
Subject: bug#42291: data service: Show list of files and allow qeuerying
Date: Fri, 10 Jul 2020 03:52:16 +0200	[thread overview]
Message-ID: <20200710015216.GA2523@LionPure> (raw)
In-Reply-To: <863661ca6m.fsf@gmail.com>

Hi

On +2020-07-09 11:25:05 +0200, zimoun wrote:
> Dear,
> 
> +Pierre because I am not sure he reads carefully debuugs. ;-)
> 
> On Thu, 09 Jul 2020 at 10:13, Hartmut Goebel <h.goebel@crazy-compilers.com> wrote:
> > Serverity: wishlist
> > I often find myself checking the content of a package. For this I
> > would like to be able to inspect the list of files in a package, or
> > even query for a specific file.
> 
> Pierre proposed "guix filesearch" some time ago.
> 
> https://lists.gnu.org/archive/html/guix-devel/2019-03/msg00236.html
> 
> 
> > This is much like Debian does in "list of files" for each package (e.g. <https://packages.debian.org/en/buster/amd64/ejabberd-mod-cron/filelist>) and with "Search the contents of packages" <https://www.debian.org/distrib/packages#search_contents>
> 
> Yes, it could be nice to have that in the Data Service.
>

Since this is about listing files, seems like it wouldn't be that hard to provide
a file globbing selection option like find dir -iname globexpr (pass through to find itself?)
(hm, also -newerct timespec can be a handy find opt)
and/or output control like "stat -c 'formatstring'" (likewise pass through to stat) ?
Also, ls-borrowed options like -B -1 -d -A might be nice.

If you want to consider the general problem of inspecting arbitrary object component details,
lsblk -o,selected,fields,listed,here  might be a good model (including -n option).

I think it would be nice if all object detail listing functions would converge in design
to a few consistent ways of specifying source and output options, so we wouldn't have
to re-invent "$(foo -dumpalot|sed -E ad_hoc_hack)" so much.

Are there any system design guidelines for converging?

BTW, please preserve cli and info retrieval independence from GUI systems,
(except when GUI preferences and parameters are the objects being inspected,
of course, but even then, minimize entanglements :)
    
> 
> All the best,
> simon
> 
> 
> 

-- 
Regards,
Bengt Richter




  parent reply	other threads:[~2020-07-10  1:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09  8:13 bug#42291: data service: Show list of files and allow qeuerying Hartmut Goebel
2020-07-09  9:25 ` zimoun
2020-07-09  9:34   ` Pierre Neidhardt
2020-07-10  1:52   ` Bengt Richter [this message]
2020-07-13 19:29 ` Christopher Baines

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=20200710015216.GA2523@LionPure \
    --to=bokr@bokr.com \
    --cc=42291@debbugs.gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    --cc=mail@ambrevar.xyz \
    --cc=zimon.toutoune@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.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).