[gobolinux-devel] Re: ISO build process
mla-gobo at forrussia.org
Fri Dec 9 07:10:34 GMT 2005
On Thursday 08 December 2005 22:52, Hisham Muhammad wrote:
> On 12/8/05, Jonatan Liljedahl <lijon at kymatica.com> wrote:
> > but one could as
> > well put them in a custom /Programs entry.
> I think that's messy, reminds me of /usr/local. I wouldn't like to
> answer the question "how do I install a font?" saying "well, you see,
> create a bogus Programs entry and drop it there so it can be
> linked..." :) but I understand the appeal of something like
> /Programs/Xorg-Fonts or InstallPackage Artwiz-Fonts. Need to give it
> some thought.
Personally, I don't like the idea of mixing metaphors. /Programs implies
just that: the contents are programs and applications (and related files, of
course, but the primary metaphor is of executables), which fonts don't fit
into. In addition, it's preferable to manage fonts through some sort of GUI
interface, like what KDE/GNOME/OSX/Windows provide for fonts. Let me give an
example of what I recently did: I wanted the Blue Highway font for a
newsletter I'm doing, so I installed the ttf-larabie-straight package. There
are 154 fonts in that package (including all the bold, italic, and bold
italic variations). Now, what is more likely: that I will keep all of them,
and when I no longer need the Blue Highway font, uninstall the entire
package, or go through them all, select the ones I like, and delete the rest?
I would suggest that the latter is the more likely scenario. I don't have a
problem with InstallPackage Larabie-Straight-Fonts, but I doubt that the need
to uninstall the package will ever really arise. Generally, if people feel in
the mood to clean house, they go through the font-viewer program and pluck
out the ones they never use/don't like/etc.
> Like I said in an earlier post, I see plugins going more naturally
> into Programs than codecs (which have more of that "fetch a file and
> drop it there" nature like fonts, and we're usually not allowed to
> make packages for them, anyway), which I could see moving into
Just to point out a small flaw in renaming the directory /Files/MPlayer,
what if another program comes along and uses the same codecs? Doesn't
transcode do that? The codecs can be used by various programs, anyone of
which may be removed in favor of another. I think that keeping /Files/Codecs
is probably for the best. Plus, other codecs that aren't specific to MPlayer
can be installed there as well.
I do think, however, that plugins could be installed in the same
subdirectory as the program that uses them, if their usage is limited only to
that specific program. This could cut down on polluting /Programs with
superfluous directories--just think about Firefox and Thunderbird extensions!
They could go into a special directory, like /Programs/Firefox/Plugins.
However, I still think that cross-program plugins (like the various web
plugins that can be used by different browsers) should be kept
in /Files/Plugins. The main question is this: are there many cross-program
plugins that can be packaged with Gobo? If there are, then it might be worth
storing such plugins in their own /Programs subdirectory. Otherwise, I don't
see the value over /Files/Plugins.
More information about the gobolinux-devel