[Bug 248649] Review Request: alliance - Alliance VLSI CAD Sytem

bugzilla at redhat.com bugzilla at redhat.com
Wed Jul 18 20:48:11 UTC 2007


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: alliance -  Alliance VLSI CAD Sytem


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248649





------- Additional Comments From kwizart at gmail.com  2007-07-18 16:48 EST -------
Whether both requiring alliance or both required by alliance, if you do so,
there is no interest in splitting them...
Actually -libs sub-packages are used to provide multibs compatibily on lib64
systems. This needed to have Requires %{main}-libs = %{evr} for -devel, but
that's all. 
- If you uses Requires %{main}-libs on main, this only requires something that
rpm would discover by itself...
- If you uses Requires %{main} on -libs, then you will break multilibs
compatibilty because you will bring i386 binaries into x86_64 repository (and
binaries will share the same namespace in %{_bindir} which is wrong )

A good way to have multilibs compatibilty would be to have your prefix in
%{_libdir}/alliance (with datadir shared in %{_datadir}/alliance if relevant)

About headers, If you can sort them, you can have %{_libdir}/alliance/include
for runtime (with main ) and %{_includedir}/alliance for devel (or runtime
headers in datadir - but i expect it will break some alliance_top prefix ?!)

That could be a good idea if you can uses relative path to find headers to have
them in %{_datadir}/alliance/include if you have examples in
%{_datadir}/alliance/examples , maybe...)

More Answears:
1 / leave this as is work for now...
4 / If upsteam change the name of the patches, you will need to import them into cvs
5 I mean the Menues indeed - I've experienced some problems whith packages that
do not handle this in %post, so i don't know if this is mandatory or should.
(depend if Minetype is present... anayway it seems not)
7 / indeed
9 / I still do not understand why you need to cp -pr them in "." since you do
uses thoses files but thoses present in doc/*
10 / Can you see at which step this /usr/lib/debug directory is created in
build.log ?

16 / alliance-examples would be fine as the content is really differents than
-docs... (for example -docs may not requires main whereas examples will requires
it - because examples may live in %{_datadir}/alliance )





-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




More information about the package-review mailing list