> 2. Both packages install to exactly the same location
> and deliver the same files, only one contains i386,
> one has SPARC.
That's not a problem, nor is it an error.
> OK, so are package writers meant to put files for
> different architectures into separate directories?
You could, but you sho
For stuff that doesn't distinguish between ARCH's, this is tricky
because the same packages can be used in different contexts:
On a personal workstation, you would expect
pkgadd
to install things in (say) /usr/bin where you can use them
directly in your PATH.
But, what if you run a serv
> where did you downloaded the package from? Looking
> pkginfo of our
> UNWfirefox, there is an ARCH field which means pkgadd
> should check that
> against the platform installing to and should at
> least give you warning
> if not stop installing.
I've sort of got into the habit with pkgadd of
pkginfo -x -d /blabla/spool/pkg BLABLAfirefox-package
If there is no ARCH in the pkginfo's output, then it's the fault of the
packager.
If there is ARCH in the pkginfo's output, and the ARCH is not "sparc", then the
old rule applies:
"he who can read is has an advantage".
This message poste
