[Bug 2483] Review request: msttcore-fonts - TrueType core fonts for the web
https://bugzilla.rpmfusion.org/show_bug.cgi?id=2483
--- Comment #40 from Rob Janes <janes.rob(a)gmail.com> 2013-05-30 02:22:26 CEST ---
Alec L, well, i'm pretty sure i understand the comments you mentioned.
comment #5, Thorsten Leemhuis, implies lots is wrong.
1. post scripts that dump files that aren't tracked by rpm are wrong. (fixed -
the files are now tracked by rpm.)
2. long post scripts are wrong. (I don't agree, but changed it to comply by
moving the functionality into a shell script that is installed by the rpm)
3. would prefer a two step process where the rpm installs a script, that can be
called by a user to install the fonts.
4. suggests akmods extension.
comment #14, Nicolas Chauvet
1. visit website with eula, download stuff manually, run rpmbuild, install rpm.
Seeing as my goal was to have a one liner, a simple rpm -i or yum install to do
everything, that could be batched and not force someone to hit enter on the
eula, these suggestions seem to be in the other direction, something other than
ease of use.
Since you seemed to want a manual process with a spec file and rpmbuild, I
pointed you to what already exists.
It's not really what I want to do though. I made a rpm that's really easy to
use, and I'd like to help people who want to use it, use it.
that's all.
I understand your point(s) perfectly. It's just kind of not where I'm going.
i have the one liner. i have a yum repository (on sourceforge). all i need to
do is advertise. looking at sourceforge, i see that the rpm downloads are
being done about 1 million times a week. Looks to me like there is some value
in making this process easier - for the end user.
your collective suggestions have been helpful, when they were relevant to my
mission. Thanks!
i'll also add this, perhaps it might be helpful. i used to work at a place
with c++ coding guidelines, somewhat styled after google's. The guidelines
were great on paper, but it seemed they were perpetually misused, and 90% of
the code review, and critical errors flagged, were about spelling mistakes in
variable names and even in the comments. Even more significantly, bugs in the
code, easy to spot segfaults, were completely ignored or missed. Guidelines
are great, but it's important to not be pedantic and remember what the goal is.
so, if your guidelines mean for a difficult user experience if followed to the
letter, then I'll pick and choose what makes sense and ignore the rest.
thanks again.
--
Configure bugmail: https://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.