Bug 1671 - naming of package google-droid-fonts
Summary: naming of package google-droid-fonts
Status: RESOLVED DUPLICATE of bug 6634
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords: Junior_job
Depends on:
Blocks:
 
Reported: 2011-06-07 16:50 CEST by Hector Zhao
Modified: 2016-08-27 16:33 CEST (History)
4 users (show)

See Also:
Source RPM: google-droid-fonts
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Hector Zhao 2011-06-07 16:50:33 CEST 
It seems this package is imported from Fedora's repository. As all other font packages are imported from Mandriva repository, this one's name is not consistent with others' naming convention, which I believe is described at http://wiki.mandriva.com/en/Policies/Fonts#Naming

A side effect I noticed was fonts-ttf-droid mdv package could not be upgraded correctly.

Any possibility to rename this package? Thanks.
Ahmad Samir 2011-07-20 17:13:33 CEST

Assignee: bugsquad => dmorganec
Source RPM: (none) => google-droid-fonts

Comment 1 Manuel Hiebel 2011-11-01 00:34:34 CET 
as no news and dmorgan is not anymore the maintainer of this package, reassign to bugsquad

Assignee: dmorganec => bugsquad
Severity: normal => minor

Comment 2 D Morgan 2011-11-01 00:53:20 CET 
what is the policy regarding fonts ?
i think we should use fedora policy for fonts as this is well written

CC: (none) => dmorganec

Comment 3 Marja Van Waes 2011-12-27 13:00:09 CET 
(In reply to comment #2)
> what is the policy regarding fonts ?
> i think we should use fedora policy for fonts as this is well written

@ Dexter

Ours is here:

https://wiki.mageia.org/en/Fonts_packaging_policy

so package name should be like: fonts-$type-$name.

Where:

    $type would be one of:
        ttf: TrueType fonts (*.ttf)
        type1: Postscript Type1 fonts (*.pfb, *.pfa, *.afm, *.pfm)
        bitmap: fixed size, bitmapped, fonts (*.pcf, *.bdf) 

    $name would be either:
        the font name: fonts-type1-hebrew
        $foundryname-$fontname: fonts-ttf-bitstream-vera 

Fonts subpackages of non-fonts main packages should follow these naming rules too, where $foundryname can be the main package name. See also the Location section below. 

Isn't our policy very well written?

CC: (none) => marja11

Remco Rijnders 2012-04-03 06:58:07 CEST

CC: (none) => remco

Comment 4 Marja Van Waes 2012-05-26 13:08:16 CEST 
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 5 Marja Van Waes 2012-06-11 20:08:20 CEST 
the package name wasn't changed

Besides, I see more "fonts" that aren't named according to https://wiki.mageia.org/en/Fonts_packaging_policy

Keywords: NEEDINFO => (none)
Whiteboard: (none) => MGA2TOO

Manuel Hiebel 2013-08-06 22:04:05 CEST

Keywords: (none) => Junior_job

Comment 6 Samuel Verschelde 2015-05-17 19:58:13 CEST 
Still valid.

Whiteboard: MGA2TOO => (none)

Comment 7 Luke Jones 2015-12-03 10:58:55 CET 
Guidelines have been updated(small extra corrections to come) and all fonts should begin following the correct procedure.

Status: NEW => ASSIGNED
CC: (none) => luke.nukem.jones
Assignee: bugsquad => luke.nukem.jones

Rémi Verschelde 2016-05-17 14:35:21 CEST

Assignee: luke.nukem.jones => pkg-bugs

Comment 8 Samuel Verschelde 2016-08-27 16:33:23 CEST 
Can be considered a duplicate of bug 6634

*** This bug has been marked as a duplicate of bug 6634 ***

Status: ASSIGNED => RESOLVED
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.