Re: New viridian and kradio4 available

Paulo Cavalcanti <[email protected]>
Newsgroups gmane.linux.redhat.rpm.atrpms.devel
Message-ID <[email protected]>
On Sat, Jan 8, 2011 at 5:43 PM, Axel Thimm <[email protected]> wrote:

> On Sat, 2011-01-08 at 08:54 -0200, Paulo Cavalcanti wrote:
> >
> >
> > On Fri, Jan 7, 2011 at 8:28 PM, Paulo Cavalcanti <[email protected]>
> > wrote:
> >
> >
> http://people.atrpms.net/~pcavalcanti/srpms/viridian-1.2-1.fc14.src.rpm<http://people.atrpms.net/%7Epcavalcanti/srpms/viridian-1.2-1.fc14.src.rpm>
> >
> >
> http://people.atrpms.net/~pcavalcanti/srpms/kradio4-4.0.2-1.fc14.src.rpm<http://people.atrpms.net/%7Epcavalcanti/srpms/kradio4-4.0.2-1.fc14.src.rpm>
> >
> >         Please, use --with rhel for rhel5 when building viridian.
> >
> >         Thanks.
> >
> >
> >
> > Axel,
> >
> > I stripped kradio4 libs, but this is only necessary when building with
> > ffmpeg.
> >
> > Then I realized that you are building ffmpeg using
> > --disable-stripping.
> >
> > Does this make any difference or I shouldn't have stripped kradio4?
>
> "Modern" rpm automatically strips anything out into debuginfo packages,
> so usually you don't want to have the build process itself strip out the
> debug symbols. If you aren't installing debuginfo packages for any
> related purpose the outcome should be the same.
>
>
That is what I thought. But the version I ship to Fedora without ffmpeg,
does not need stripping,
and if I do, the debug info package is empty, as it should be.

On the other hand, the version for ATrpms with ffmpeg requires the stripping
step,
and the debug info package is not empty! (how can that be??)

Both versions were built using mock, and I can not explain the difference.
The only thing I can think of is the non stripped ffmpeg package, but I may
be completely wrong ...
Well, it does not seem to make any difference after all, because both
packages work just fine.

Thanks.

-- 
Paulo Roma Cavalcanti
LCG - UFRJ
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.