View Single Post
Old 11-15-2015, 07:02 PM   #6
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by KevinH View Post
Hi eschwartz,



Nicely done.



The output itself is only 1 page long in total and it tells you everything. So a quick visual inspection will tell you anything you want.

I can split out the extra Python external packages such as cssutils, cssselect, PIL, html5lib, six, into their own reporting section. That said if you or other linux distributors treat them differently from other python 3 packages, some future plugin may fail generating an unneeded bug report and more inconsistencies across platforms. I would prefer to keep all versions of Sigil with the exact same capabilties just to be safe and consistent and to make support easier.
Quick visual inspection that requires you to fully read each line.
Maybe instead you could colorize it (red warning) or print "**** FAILED ****" if the plugin runner doesn't support color (probably not...)

It isn't that big a deal, it's just that currently it doesn't stand out very well.


As for optional components, linux distributors like splitting out optdepends, and expect users to know what they're doing.
apt-based systems can use Recommends, which I believe is installed by default -- an advanced setting lets you only install the minimal packages necessary, and advanced users are expected to know what they are doing later on down the line.
ArchLinux is a "user-centric, not user-friendly" distro, and we are expected to make note of the "optional dependencies for ____" list in pacman's output.

Perhaps, like the Failed checks, you can simply add a Recommended status but still group them as you do now. I'm just floating ideas here.

Again, it's your choice, but packagers may appreciate the information since it helps them figure out how to write the dependency list based on their preferred guidelines.

Quote:
I only just added it to the Mac OSX building docs before I posted it here. The Linux docs will get a similar treatment but there are only so many hours of volunteer time this weekend. Before we release Sigil-0.9.1, we'll make that change.

Thanks,
KevinH
Thanks. Just wanted to make sure you were aware.
eschwartz is offline   Reply With Quote