Re: Build error at creating fonts packages in OBS

At Thu, 01 Oct 2009 18:21:25 +0900,
Satoru Matsumoto wrote:
> 
> Takashi Iwai wrote:
> 
> > There are no %prep and %setup sections in your spec file.
> > Without these sections, the source files aren't expanded properly.
> 
> Putting %prep and %setup sections without content is just enough ?

If you convert the main source to a tar.gz or tar.bz2, rpm will
expand it automatically.  So yes, if you do so, single %prep and
%setup lines should suffice.

> > IIRC, rpm can't handle zip file as the source, so you need to expand
> > it manually via unzip.  But, it'd be much easier if you re-pack the
> > contents to a tar.bz2.
> 
> I see.
> 
> > Also, I'd suggest to rename to all lower letters as convention.
> > Maybe it'd be better to have -fonts (or -font) prefix in the package
> > name, so that it gets clearer what kind of package it is.
> > I'm going to rename monapo package to monapo-font as well.
> 
> Hmmm, in which cases should we use capital letters in package names ?
> For example, in case if the names are kinds of trademarks ?

Depends.  If the program has to be such (e.g. NetworkManager or
DeviceKit), then we'd take as is.  But I don't think this is the case
of Konatsu font, so better to follow the convention.

> > Anyway, you'd be better to build the package locally on your machine
> > before submitting to the public repository.  M17N:Devel is a test
> > project, so it's almost harmless, though.
> 
> OK. I've removed the package once and I will try to build it in my home
> repo first. - Unfortunatly, I haven't built local build environment in
> my machine yet. :-P

That's easy and much faster for testing.  Just give it a try.

> BTW, are there any suggested procedures to submit new packages to the
> public repositories ?

osc submitreq is the standard way.  No matter where to.
You can give ack by yourself.


Takashi
-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]