From: Sen Hastings <sen@phobosdpl.com>
To: Arnout Vandecappelle <arnout@mind.be>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/3] support/scripts/pkg-stats: adjust column widths
Date: Tue, 2 Aug 2022 15:30:06 -0500 [thread overview]
Message-ID: <fabcfaf5-eaa9-930f-4422-1b7f0980e615@phobosdpl.com> (raw)
In-Reply-To: <8e538839-349e-09db-cf02-8b8b4ee0abae@mind.be>
On 8/1/22 13:11, Arnout Vandecappelle wrote:
> Hi Sen,
>
> On 01/08/2022 19:04, Thomas Petazzoni via buildroot wrote:
>> On Thu, 28 Jul 2022 18:23:56 -0500
>> Sen Hastings <sen@phobosdpl.com> wrote:
>>
>>> This adjusts the column widths, mostly for asthetics/legibility.
>>>
>>> It is primarily for chrome based browsers, which like to
>>> linebreak on explicit hyphens, meaning every CVE takes multiple lines.
>>>
>>> see: https://github.com/w3c/csswg-drafts/issues/3434
>>>
>>> Signed-off-by: Sen Hastings <sen@phobosdpl.com>
>>
>> This doesn't behave extremely well here as it prevents wrapping of the
>> package .mk file path in the first column, making this first column
>> larger than it was. I guess wrapping on "/" would be ideally for this
>> first column.
>>
>> Here the table continues to exceed the width of my large browser window
>> (with or without this patch), which is not very nice :-/
>
> Since pkg-stats takes a pretty long time to run, it would be nice if
> you could publish the output of pkg-stats (with no .config) somewhere so
> we can look at it directly and notice these things easier.>
Yeah, these weird edge cases only crop up when you build all the
packages... which requires building all the packages.
My usual dev cycle is to pull master.html, edit the js in situ and then
move it back into the pkg-stats script. I usually only run pkg-stats
against a fairly simple defconfig like pc_x86_64_efi or my own personal
project. I guess I should do a full build of master weekly, and perhaps
a nightly run of pkg-stats, then host the html somewhere. And perhaps I
should look into parsing the json output into html...
Sincerely,
Sen H.
> Regards,
> Arnout
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-02 20:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 23:23 [Buildroot] [PATCH 1/3] support/scripts/pkg-stats: make cells with many CVEs collapsible Sen Hastings
2022-07-28 23:23 ` [Buildroot] [PATCH 2/3] support/scripts/pkg-stats: adjust column widths Sen Hastings
2022-08-01 17:04 ` Thomas Petazzoni via buildroot
2022-08-01 18:11 ` Arnout Vandecappelle
2022-08-02 20:30 ` Sen Hastings [this message]
2022-08-02 22:04 ` Thomas Petazzoni via buildroot
2022-07-28 23:23 ` [Buildroot] [PATCH 3/3] support/scripts/pkg-stats: re-implement the sortable_hint Sen Hastings
2022-08-01 17:02 ` Thomas Petazzoni via buildroot
2022-08-01 17:02 ` [Buildroot] [PATCH 1/3] support/scripts/pkg-stats: make cells with many CVEs collapsible Thomas Petazzoni via buildroot
[not found] <76c8fcd6-d477-7cbe-dcc5-b382d65f3498@phobosdpl.com>
2022-08-02 19:47 ` [Buildroot] [PATCH 2/3] support/scripts/pkg-stats: adjust column widths Sen Hastings
2022-08-02 21:18 ` Thomas Petazzoni via buildroot
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=fabcfaf5-eaa9-930f-4422-1b7f0980e615@phobosdpl.com \
--to=sen@phobosdpl.com \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.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