https://bugzilla.rpmfusion.org/show_bug.cgi?id=2483
--- Comment #35 from Rob Janes <janes.rob(a)gmail.com> 2013-05-28 15:31:34 CEST ---
re font files as code ... ok, postscript fonts too, but I still don't think
they fall in the spirit of the guideline, which is for "real" code, sorry,
don't mean to insult any font builders out there.
re inclusion of cab files in rpm in some format. my sense is that this is
treading on thin ice. nobody has gone down this path. ok, forgetting about
the legal stuff, here's what's needed:
* cpio file in the source directory
* this cpio file is removed in the post section. need some rpm magic so that
there are no complaints. i suppose it could be truncated, but it would
be best to remove it.
* the shell script will unpack and install the ttf files.
* still need ttf stub files
since we're brainstorming about the eula, how about ...
* linux x-windows is multi user. the fonts will be used by anybody, not just
the admin.
* put the fonts behind a fuse filesystem that detects first use.
* the fuser pops up a dialogue on the users screen with the eula.
* if they agree, fuse allows access to the fonts. otherwise, it's blocked.
on a multi user system, it's likely the sysadmin will never use the fonts,
and thus his/her confirmation of the eula is meaningless. end user license
agreement.
even if we made the rpm interactive (horror of horrors) it still won't be seen
by the end user necessarily.
just brainstorming. i'm fine with gentoo config file flags. i hate the ubuntu
eula that makes batch installs impossible.
--
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.