help with source package font path

[Qianqian Fang]

hi

I thought that I sent an email asking this as followups for Bug#478891, but
just realized the email was never posted at bugzilla :(

anyway, I am still experiencing the incorrect font path error when compiling
wqy-zenhei-fonts with the new fontpackages templates. The error and my spec
file can be found at

https://bugzilla.redhat.com/show_bug.cgi?id=478891#c3
and
https://bugzilla.redhat.com/show_bug.cgi?id=478891#c4

basically, the installer first unpacked the upstream source tarball, and
then attempted to "cd wqy-zenhei-fonts-0.8.34", unfortunately, the upstream
package does not name the folder that way, simply "wqy-zenhei/", so the
installer quit.

I am wondering which variable controls the source folder name and how can I
fix this?

thank you

Qianqian

[Caius Carlos CHANCE]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Qianqian Fang wrote:
>  
>  basically, the installer first unpacked the upstream source tarball, and
>  then attempted to "cd wqy-zenhei-fonts-0.8.34", unfortunately, the
>  upstream package does not name the folder that way, simply
>  "wqy-zenhei/", so the installer quit.
>  
>  I am wondering which variable controls the source folder name and how
>  can I fix this? 
Yes, I have experienced same thing before. :)

%setup -q -n %{name}-%{version}.devel

You could set the directory extracted from tarball with any name. In
above example, %{name}-%{version}.devel

i.e. '%setup -q -n wqy-zenhei-fonts-0.8.34' should works for you, but it
should be better to have %{fontname}-fonts-%{version} like naming.

Best Regards,
kaio


- --
Caius Chance, Soft Eng, I18N, Red Hat APAC, cchance AT redhat DOT com
JP (Qual), RHCE, MCSE, CCNA, JLPT4, http://apac.redhat.com/disclaimer
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkmQyRAACgkQmo+B7bGj5dIryQCdE82uCgvJjc+QTDP3nfUUw0NX
> bdgAnji03KKWc+ofU2yF3wdaEqEFR++E
> =Vw+W
> -----END PGP SIGNATURE-----

[Qianqian Fang]

it works! thank you

Qianqian

Caius "kaio" Chance wrote:
>  Yes, I have experienced same thing before. :)
>
>  %setup -q -n %{name}-%{version}.devel
>
>  You could set the directory extracted from tarball with any name. In
>  above example, %{name}-%{version}.devel
>
>  i.e. '%setup -q -n wqy-zenhei-fonts-0.8.34' should works for you, but it
>  should be better to have %{fontname}-fonts-%{version} like naming.
>
>  Best Regards,
>  kaio
>
>
>  - --
>  Caius Chance, Soft Eng, I18N, Red Hat APAC, cchance AT redhat DOT com
>  JP (Qual), RHCE, MCSE, CCNA, JLPT4, http://apac.redhat.com/disclaimer
> >  -----BEGIN PGP SIGNATURE-----
> >  Version: GnuPG v1.4.9 (GNU/Linux)
> >  Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
> >
> >  iEYEARECAAYFAkmQyRAACgkQmo+B7bGj5dIryQCdE82uCgvJjc+QTDP3nfUUw0NX
> >  bdgAnji03KKWc+ofU2yF3wdaEqEFR++E
> >  =Vw+W
> >  -----END PGP SIGNATURE----- 
>

[Qianqian Fang]

one more question: for font packages which do not have any fontconfig
files, how should I formulate the %_font_pkg line? One of the examples is
wqy-unibit-fonts, I kept only the font file following -f but rpm failed 
when
compiling.

Qianqian

Qianqian Fang wrote:
>  it works! thank you
>
>  Qianqian
>
>  Caius "kaio" Chance wrote:
> > Yes, I have experienced same thing before. :)
> >
> > %setup -q -n %{name}-%{version}.devel
> >
> > You could set the directory extracted from tarball with any name. In
> > above example, %{name}-%{version}.devel
> >
> > i.e. '%setup -q -n wqy-zenhei-fonts-0.8.34' should works for you, but it
> > should be better to have %{fontname}-fonts-%{version} like naming.
> >
> > Best Regards,
> > kaio
> >
> >
> > - --
> > Caius Chance, Soft Eng, I18N, Red Hat APAC, cchance AT redhat DOT com
> > JP (Qual), RHCE, MCSE, CCNA, JLPT4, http://apac.redhat.com/disclaimer
> > > -----BEGIN PGP SIGNATURE-----
> > > Version: GnuPG v1.4.9 (GNU/Linux)
> > > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
> > >
> > > iEYEARECAAYFAkmQyRAACgkQmo+B7bGj5dIryQCdE82uCgvJjc+QTDP3nfUUw0NX
> > > bdgAnji03KKWc+ofU2yF3wdaEqEFR++E
> > > =Vw+W
> > > -----END PGP SIGNATURE----- 
> >
> >   
>
>  _______________________________________________
>  Fedora-fonts-list mailing list
>  Fedora-fonts-list(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-fonts-list
>

[Caius Carlos CHANCE]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Qianqian Fang wrote:
>  one more question: for font packages which do not have any
> fontconfig
>  files, how should I formulate the %_font_pkg line? One of the examples is
>  wqy-unibit-fonts, I kept only the font file following -f but rpm failed
>  when
>  compiling. 
You need to create that manually. Please kindly use the templates in
'fontpackages' sources.

kaio


- --
Caius Chance, Soft Eng, I18N, Red Hat APAC, cchance AT redhat DOT com
JP (Qual), RHCE, MCSE, CCNA, JLPT4, http://apac.redhat.com/disclaimer
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkmRI08ACgkQmo+B7bGj5dLmFgCfYyITTNRIpihOqZkz0hcrLBPP
> vgYAnR5f9zwZXUbcCiDdxoXD24KF8xbo
> =K0e4
> -----END PGP SIGNATURE-----

[Qianqian Fang]

Caius "kaio" Chance wrote:
>  You need to create that manually. Please kindly use the templates in
>  'fontpackages' sources.
>
>  kaio
>
>     
ok, I took out the -f from _font_pkg and now it works with just having 
the font file.

[Nicolas Mailhot]

Le mardi 10 février 2009 à 01:36 -0500, Qianqian Fang a écrit :
>  one more question: for font packages which do not have any
> fontconfig
>  files, how should I formulate the %_font_pkg line? One of the examples is
>  wqy-unibit-fonts, I kept only the font file following -f but rpm failed 
>  when compiling. 
-f is the fontconfig file switch so you can never have -f <nothing>
font_files

However Caius is right making the effort to produce a fontconfig file
for every font subpackage is much preferred

-- 
Nicolas Mailhot