From: zimoun <zimon.toutoune@gmail.com>
To: "Liliana Marie Prikler" <liliana.prikler@ist.tugraz.at>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: 54000@debbugs.gnu.org
Subject: [bug#54000] [PATCH 0/2] Not showing upgraded/added packages in 'guix pull'
Date: Thu, 17 Feb 2022 13:04:03 +0100 [thread overview]
Message-ID: <86ley94s3w.fsf@gmail.com> (raw)
In-Reply-To: <31aeb5561e8aad5b5d5b235ff326f145a84863e3.camel@ist.tugraz.at>
Hi Liliana,
On Thu, 17 Feb 2022 at 11:30, Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> wrote:
>> Is it an actual use case or speculation?
>
> That's a use case. While --dry-run exists, I don't really want it to
> serve double duty here. If I previously guix pulled and only three new
> packages were added, none of which I'm interested in, I would not have
> to meaninglessly run further build commands like guix package or guix
> system. Even if the list is potentially longer, I could visually grep
> for a few packages I'm interested in and determine whether it'd make
> sense to build now or wait for a little while as I'm processing other
> things.
Stats, ~24 updates and ~13 additions per day on average (over the past
year). If you pull twice a day, then yes you can read this information.
But, I bet people pull once a week, at best, so it looks like more
“noise“ and I guess most people miss the news.
About grepping, it is not straightforward. For instance, I get this:
--8<---------------cut here---------------start------------->8---
$ guix pull --news | grep python
openshadinglanguage, perl-date-range, pgcli, plfit, poweralertd, pproxy, python-aiosignal, python-android-backup,
python-asdf-astropy, python-astral, python-astropy-healpix, python-astroquery, python-canvasapi, python-cmarkgfm,
python-cucumber-tag-expressions, python-cython-next, python-doit, python-esprima, python-executing,
python-flask-assets, python-flit-core-bootstrap, python-frozenlist, python-fs, python-geojson, python-gwcs,
python-ipython-sql, python-markdownify, python-miio, python-pgspecial, python-photutils, python-phpserialize,
python-piexif, python-psycopg, python-psycopg-pool, python-pydbus, python-pyftpdlib, python-pylru, python-pyowm,
python-pypdf3, python-pyrss2gen, python-pyscss, python-pysendfile, python-pystitcher,
python-pytest-doctest-custom, python-pytest-metadata, python-pytest-pydocstyle, python-pyvo, python-reedsolo,
python-regions, python-retry, python-roundrobin, python-sarge, python-sentry-sdk, python-setuptools-rust,
python-sphinx-click, python-sphinxcontrib-apidoc, python-tomli-w, python-tweepy, python-typeguard,
--8<---------------cut here---------------end--------------->8---
So I do not think the current display is adequate for grepping.
Somehow, the feature you want should be separated. For instance,
guix pull --updated
guix pull --added
guix pull --new-versions
> In general, it doesn't have to be named ‘--news --details’, but a means
> of diffing two generations via the CLI -- in particular the current one
> to the last -- would be very welcome, because then all information we
> previously had would still be available quite easily, albeit no longer
> printed by default.
That feature is interesting but it appears to me orthogonal with the
current proposal.
Cheers,
simon
next prev parent reply other threads:[~2022-02-17 12:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 16:38 [bug#54000] [PATCH 0/2] Not showing upgraded/added packages in 'guix pull' Ludovic Courtès
2022-02-14 16:41 ` [bug#54000] [PATCH 1/2] pull: '--news' no longer shows package lists Ludovic Courtès
2022-02-14 16:41 ` [bug#54000] [PATCH 2/2] pull: No longer print upgraded/added packages upon completion Ludovic Courtès
2022-02-15 13:55 ` [bug#54000] [PATCH 0/2] Not showing upgraded/added packages in 'guix pull' Liliana Marie Prikler
2022-02-17 10:19 ` Ludovic Courtès
2022-02-17 10:30 ` Liliana Marie Prikler
2022-02-17 12:04 ` zimoun [this message]
2022-02-17 12:52 ` Liliana Marie Prikler
2022-02-17 14:41 ` zimoun
2022-02-18 9:08 ` Ludovic Courtès
2022-02-18 9:20 ` Liliana Marie Prikler
2022-02-27 22:15 ` bug#54000: " Ludovic Courtès
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=86ley94s3w.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=54000@debbugs.gnu.org \
--cc=liliana.prikler@ist.tugraz.at \
--cc=ludo@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/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).