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

[bugzilla at redhat.com]

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 cgoorah at yahoo.com.au  2007-08-01 12:09 EST -------
(In reply to comment #19)
>  * As previously talked with the prefix discution. $ALLIANCE_TOP is not arch
> independant from how upstream use it.

chitlesh(~)[0]$ll /usr/share/alliance/
total 4
drwxr-xr-x 10 root root 4096 Jul 29 17:55 cells
lrwxrwxrwx  1 root root   21 Jul 29 17:55 etc -> ../../../etc/alliance
lrwxrwxrwx  1 root root   29 Jul 29 17:55 
include -> ../../../usr/include/alliance
lrwxrwxrwx  1 root root   25 Jul 29 17:55 lib -> ../../../usr/lib/alliance

The symbolic links are here to protect hardcorded bits of the codes that 
aren't dynamically set up during %configure. These symbolics links are here to 
meet _functionality_ when all the %{_bindir}/* are used at once( on a Makefile 
for example.) 

Please take note that libraries are placed at %{_libdir}/%{name} 
during %configure --libdir=%{_libdir}/%{name}

As from the only "real" directory, cells which contains "technology files". 
Text files which specify the design rules of the respective technology.

The latter is _NOT_ a must in the alliance distribution. Since the user might 
want to use his/her technology. for example from:
* http://www.vlsitechnology.org/
* commercial technologies

However the included cells are present so that one who doesn't have his/her 
own technology can use them for the first time.

I hope I clarified that this is not arch-dependent, and should not 
be %{_libdir} but %{_datadir}

Please also note, that once alliance is in the fedora collection, i'll start 
packaging the standard cells from http://www.vlsitechnology.org/, hence those 
will be placed in  %{_datadir}, since there are only text files and images. 
Thus _not_ arch-dependent.

The way that upstream uses the $ALLIANCE_TOP variable is similar to most 
commercial vendors do.

But in my spec, these are split up in standard linux directories and made sure 
that users can still use $ALLIANCE_TOP. This variable IS NOT only for 
packagers or developers but users as well.

-- 
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.