Laszlo (Laca) Peter wrote: > On Wed, 2009-06-10 at 11:07 +0100, Amanda Waite wrote: > >> Any idea why some in some of the packages built from a spec file, the >> likes of SUNWzlib and SUNWcsl show up but in others they don't. The >> > > Can you give an example where they show up in the manifest? >
http://jucr.opensolaris.org/review/packages/429 Produced: http://jucr.opensolaris.org/pending/manifest/0/ploticus%402.41%2C5.11-0.101%3A20090519T165316Z and then 2 weeks later, produced: http://jucr.opensolaris.org/pending/manifest/0/ploticus%402.41%2C5.11-0.101%3A20090601T230557Z Josh (who submitted it) will know if anything changed in the spec file between the builds, but the latest package was built with the spec file that's there currently. > >> implication is that on some of the build zones these are available as >> IPS packages and on others they are available as SVR4 packages and that >> only the IPS versions appear as dependencies in the manifest. >> >> Also Christian says that the zones have a minimal set of packages >> installed (SVR4 packages), which means the vast majority of packages >> would be installed from IPS which suggests that the issue should only >> affect the base packages. If Drupal wants SUNWapch22 it should be >> installed from IPS and then SUNWapch22 would appear as a dependency in >> the manifest. It doesn't. >> > > Hmm... SUNWapch22 is a Requires, not a BuildRequires, so I suspect > that jucr does not install it in the build zone. Which is interesting, > because this is a situation that pkgbuild needs to be able to deal > with, even though the package is not installed. I will have to think > about this. > We have lots of examples of that problem. Amanda > Laca > > >
