Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=435015
Mamoru Tasaka <mtasaka(a)ioa.s.u-tokyo.ac.jp> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mtasaka(a)ioa.s.u-tokyo.ac.jp
--- Comment #10 from Mamoru Tasaka <mtasaka(a)ioa.s.u-tokyo.ac.jp> 2008-10-24
13:58:35 EDT ---
Umm.. I cannot guess why you want to name binary rpm names as
libgpp4 and libgpp4-devel. Simply gpp4 and gpp4-devel is better.
Debian seems to name binary debs providing system wide libraries
as libXXXXX (like libpango1.0-0) while Fedora simply names binary
rpms using source tarball name as much as possible (like pango)
(For me I maintain oniguruma while debian uses libonig as binary
deb names...)
https://fedoraproject.org/wiki/Packaging/NamingGuidelines#General_Naming
By the way rebuild fails on ppc64:
http://koji.fedoraproject.org/koji/taskinfo?taskID=901509
Now that I am sponsoring you, you can try to rebuild arbitrary srpms
on koji by
$ koji build --scratch <target> <srpm_you_want_to_try>
where target can be dist-f11, dist-f10, dist-f9-updates-candidate
or dist-f8-updates-candidate.
If the build is successful, the rebuilt rpms and some logs are
put for one week or so under:
http://koji.fedoraproject.org/scratch/<your_FAS_name>/task_<task...
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.