Re: [gentoo-dev] ebuilds which install fonts

Re: [gentoo-dev] ebuilds which install fonts

[Nathaniel Grady]

On Mon, May 20, 2002 at 04:40:54PM +0900, Ryan Shaw wrote: 
> fonts. the ebuilds i have seen thus far 
> which install fonts (freefonts and x11fonts-jmk) 
> create new subdirectories of of /usr/lib/X11/fonts. 
> this seems bad though, since it means that 
> a new FontPath needs to be added to XF86Config 

What about having multiple, slightly different, copies of, say, the
"times" font from different packages. I've run into this several times.
For an example see 75dpi vs 100dpi directories, a contrived example I
admit, but one everyone has. I really think keeping font packages
separate is a good idea because eventually you'll run into a collision.

Just my 2 Cents :)

-- 

--Nathaniel Grady

   /*\              ASCII RIBBON CAMPAIGN
   \ /              - AGAINST HTML EMAIL
    X               - AGAINST MS ATTACHMENTS
   / \
------------------------------------------------
-- 

--Nathaniel Grady

   /*\              ASCII RIBBON CAMPAIGN
   \ /              - AGAINST HTML EMAIL
    X               - AGAINST MS ATTACHMENTS
   / \
------------------------------------------------

Re: [gentoo-dev] ebuilds which install fonts

[Ryan Shaw]

Nathaniel wrote:

> On Mon, May 20, 2002 at 04:40:54PM +0900, Ryan Shaw wrote: 
>
> > fonts. the ebuilds i have seen thus far 
> > which install fonts (freefonts and x11fonts-jmk) 
> > create new subdirectories of of /usr/lib/X11/fonts. 
> > this seems bad though, since it means that 
> > a new FontPath needs to be added to XF86Config 
> 
> What about having multiple, slightly different, copies of, say, the
> "times" font from different packages. I've run into this several times.
> For an example see 75dpi vs 100dpi directories, a contrived example I
> admit, but one everyone has. I really think keeping font packages
> separate is a good idea because eventually you'll run into a collision.

i think this is something that could be worked out among
the ebuild maintainers. plus, sticking to the standard
directories makes it clear what type of fonts they are.
if i just install a bunch of fonts in /usr/lib/X11/fonts/foo,
how does the user know if these foo fonts are Type1, Speedo,
TrueType, CID, or bitmap fonts? Sure, they can examine the
font files, but what a pain...

rbs 

Re: [gentoo-dev] ebuilds which install fonts

[Bjarke Sørensen]

On Tue, May 21, 2002 at 09:27:56AM +0900, Ryan Shaw wrote:
> i think this is something that could be worked out among
> the ebuild maintainers. plus, sticking to the standard
> directories makes it clear what type of fonts they are.
> if i just install a bunch of fonts in /usr/lib/X11/fonts/foo,
> how does the user know if these foo fonts are Type1, Speedo,
> TrueType, CID, or bitmap fonts? Sure, they can examine the
> font files, but what a pain...

The general guideline is:
  "Stick to FHS 2.2: http://www.pathname.com/fhs/2.2/"

Right?
-- 
| Bjarke Sørensen  /  9000.WASD 
|
|  There are 10 types of people in this world:
|  Those who understand binary, and those who don't.

Re: [gentoo-dev] ebuilds which install fonts

[Ryan Shaw]

Bjarke wrote:

> On Tue, May 21, 2002 at 09:27:56AM +0900, Ryan Shaw wrote:
>
> > i think this is something that could be worked out among
> > the ebuild maintainers. plus, sticking to the standard
> > directories makes it clear what type of fonts they are.
> > if i just install a bunch of fonts in /usr/lib/X11/fonts/foo,
> > how does the user know if these foo fonts are Type1, Speedo,
> > TrueType, CID, or bitmap fonts? Sure, they can examine the
> > font files, but what a pain...
> 
> The general guideline is:
>   "Stick to FHS 2.2: http://www.pathname.com/fhs/2.2/"

Unfortunately, the FHS does not specify that far down 
the hierarchy. It just goes as far as /usr/lib/X11.

Anyway, I already completed and submitted my ebuild.
It installs fonts under /usr/lib/X11/fonts/truetype,
and rebuild fonts.scale and fonts.dir after merging
and unmerging.

Ryan

Re: [gentoo-dev] ebuilds which install fonts

[nate]

On Mon, May 20, 2002 at 04:40:54PM +0900, Ryan Shaw wrote:
> fonts. the ebuilds i have seen thus far 
> which install fonts (freefonts and x11fonts-jmk)
> create new subdirectories of of /usr/lib/X11/fonts.
> this seems bad though, since it means that 
> a new FontPath needs to be added to XF86Config 

What about having multiple, slightly different, copies of, say, the
"times" font from different packages. I've run into this several times.
For an example see 75dpi vs 100dpi directories, a contrived example I
admit, but one everyone has. I really think keeping font packages
separate is a good idea because eventually you're likely to run into
this I think.

Just my 2 cents :)

-- 

--Nathaniel Grady

   /*\              ASCII RIBBON CAMPAIGN
   \ /              - AGAINST HTML EMAIL
    X               - AGAINST MS ATTACHMENTS
   / \
------------------------------------------------

[gentoo-dev] ebuilds which install fonts

[Ryan Shaw]

i would like to create some ebuilds for some 
free font collections, but i am not sure what
the standard is for ebuilds which install
fonts. the ebuilds i have seen thus far 
which install fonts (freefonts and x11fonts-jmk)
create new subdirectories of of /usr/lib/X11/fonts.

this seems bad though, since it means that 
a new FontPath needs to be added to XF86Config 
every time new fonts are installed. why not
just stick to the standard approach of adding
fonts to the subdir of /usr/lib/X11/fonts which 
matches their type (Type1, truetype, etc.) and 
rebuilding the proper index files for fonts of 
that type?

ryan

Re: [gentoo-dev] ebuilds which install fonts

[Bjarke Sørensen]

On Mon, May 20, 2002 at 04:40:54PM +0900, Ryan Shaw wrote:
> fonts. the ebuilds i have seen thus far 
> which install fonts (freefonts and x11fonts-jmk)
> create new subdirectories of of /usr/lib/X11/fonts.

Keeping different things apart.


> this seems bad though, since it means that 
> a new FontPath needs to be added to XF86Config 

Is that so bad/hard?


> just stick to the standard approach of adding
> fonts to the subdir of /usr/lib/X11/fonts which 
> matches their type (Type1, truetype, etc.) and 
> rebuilding the proper index files for fonts of 
> that type?

Of course portage handles the uninstall (and deletion) for you, so
that's not an issue.

But in general I think people just go with their way when making
ebuild; why be different an conform?
-- 
| Bjarke Sørensen  /  9000.WASD 
|
|  There are 10 types of people in this world:
|  Those who understand binary, and those who don't.

Re: [gentoo-dev] ebuilds which install fonts

[Ryan Shaw]

Bjarke wrote:

> On Mon, May 20, 2002 at 04:40:54PM +0900, Ryan Shaw wrote:
> > fonts. the ebuilds i have seen thus far 
> > which install fonts (freefonts and x11fonts-jmk)
> > create new subdirectories of of /usr/lib/X11/fonts.
> 
> Keeping different things apart.

okay, that is an advantage.

> > this seems bad though, since it means that 
> > a new FontPath needs to be added to XF86Config 
> 
> Is that so bad/hard?

no, but then why have the ebuilds at all? ideally,
after merging a font package those fonts are available
for apps to use, otherwise the ebuild is just downloading
a tarball and unpacking it; what's the point?

> But in general I think people just go with their way when making
> ebuild; why be different an conform?

are you serious? 

ryan

Re: [gentoo-dev] ebuilds which install fonts

[Bjarke Sørensen]

On Mon, May 20, 2002 at 05:15:02PM +0900, Ryan Shaw wrote:
> > > fonts. the ebuilds i have seen thus far 
> > > which install fonts (freefonts and x11fonts-jmk)
> > > create new subdirectories of of /usr/lib/X11/fonts.
> > Keeping different things apart.
> okay, that is an advantage.

But the only one.


> > > this seems bad though, since it means that 
> > > a new FontPath needs to be added to XF86Config 
> > Is that so bad/hard?
> no, but then why have the ebuilds at all? ideally,
> after merging a font package those fonts are available
> for apps to use, otherwise the ebuild is just downloading
> a tarball and unpacking it; what's the point?

I see, so installing in /usr/lib/X11/fonts would be the wise choice.


> > But in general I think people just go with their way when making
> > ebuild; why be different an conform?
> are you serious? 

Unfortunately, yes. If everone else create new folders for their
font-bundles I don't think you should conform, but rather use your
first impression.

-- 
| Bjarke Sørensen  /  9000.WASD 
|
|  There are 10 types of people in this world:
|  Those who understand binary, and those who don't.

Re: [gentoo-dev] ebuilds which install fonts

[Ryan Shaw]

Bjarke wrote:

> > > But in general I think people just go with their way when making
> > > ebuild; why be different an conform?
> >
> > are you serious? 
> 
> Unfortunately, yes. If everone else create new folders for their
> font-bundles I don't think you should conform, but rather use your
> first impression.

okay. i won't conform to what i perceive to be bad/weird practice.
but...at some point there needs to be consensus on these sorts of
issues. if everyone who creates ebuilds just "does their own thing"
gentoo will very quickly become a mess.

ryan

Re: [gentoo-dev] ebuilds which install fonts

[maarten]

Ryan,

> just stick to the standard approach of adding
> fonts to the subdir of /usr/lib/X11/fonts which 
> matches their type (Type1, truetype, etc.) and 
> rebuilding the proper index files for fonts of 
> that type?

This looks like a great idea. Yet another ._cfg file users won't have to 
edit upon upgrade. Plus it looks like the Right Way.

cheers,
maarten