Tim,
Thanks for the quick response. I redid both the libgcc and gcc packages
taking out those files in gcc that are duplicated in libgcc and making
gcc have a require dependency on the libgcc package. The gcc package
now appears to install with no error messages.
Pkglint is very interesting, but will require some study I think to
understand fully.
Steve C.
On 09/02/12 19:06, Tim Foster wrote:
On 09/ 2/12 08:07 PM, Steven M. Christensen wrote:
IPS server, I have packages libgcc and gcc. The libgcc has just those
libraries that many packages depend on.
.
.
.
What is the solution to this? Do I need to fix the gcc or libgcc
manifests so that gcc can be installed after libgcc if the user wants
gcc at some point?
Yes - typically, you'd separate out the development aspects from the
runtime aspects of the library.
Solaris itself does this in its shipped versions of gcc:
$ pkg list -fg http://pkg.oracle.com/solaris/release *gcc* | grep 175
developer/gcc-3 (solaris) 3.4.3-0.175.0.0.0.2.537 ---
developer/gcc-45 (solaris) 4.5.2-0.175.0.0.0.2.537 ---
system/library/gcc-3-runtime (solaris) 3.4.3-0.175.0.0.0.2.537 ---
system/library/gcc-45-runtime (solaris) 4.5.2-0.175.0.0.0.2.537 ---
This way, you can ship packages that depend on the libraries delivered
in the runtime GCC package without affecting whether users can later
install the compiler.
That the error you saw:
----
# pkg install gcc
Creating Plan |
pkg install: The following packages all deliver file actions to
usr/local/lib/libstdc++.so.6:
pkg://unixpackages/[email protected],5.11-0:20120902T064823Z
pkg://unixpackages/[email protected],5.11-0:20120409T062004Z
These packages may not be installed together. Any non-conflicting set may
be, or the packages must be corrected before they can be installed.
The following packages all deliver file actions to usr/local/lib/libg2c.so:
----
can be found before publication using pkglint(1) to examine package
manifests.
pkglint can be used with one or more package manifests, but can also
reference a repository where you plan to publish that package, allowing
it to check that the package "plays well" with other packages.
Hope this helps?
cheers,
tim
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
