When renaming a package can I specify the previous build
in the version strings.
Take my apache-php5.p5m.
set name=pkg.fmri \
value=pkg:/web/server/apache-22/module/[email protected]
^^^^^^^^^^^^^^
set name=pkg.renamed value=true
set name=org.opensolaris.consolidation value=$(CONSOLIDATION)
depend fmri=web/server/apache-22/module/[email protected] \
^^^^^^^^^^^^^^
type=require
Can I specify 0.175.1.0.0.16 and then putback into what WILL be build 17
once the gate closes and is tagged with 17?
----- [email protected] wrote:
> Thanks Danek.
>
> I think I have a mostly meaningful webrev now at:
> http://jurassic.us.oracle.com/net/mogo/builds3/cmohrman/userland_php-ips-review/webrev/
>
> All the php-5_3 is based off copies of php-5_2 files so the webrev
> shows
> as diffs and not just NEW.
>
> Please have a look.
>
> To answer #4 below about upgrades.
> I'm testing mainly:
> pkg update
> for the customer running Solaris11 FCS and php-5.2 installed.
> And
> pkg install's
> for customers new to Solaris 11 or haven't installed php yet.
> And switching mediators, etc.
> This all works fine.
>
> Still working on #3 below.
> The don't think the incorporation is not the problem.
>
> craig
>
> ----- [email protected] wrote:
>
> > > 3) How do I test apache-php5.p5m with build 17 set as the
> version?
> > > I have to use 16.xxx to get all packages to update properly.
> > >
> > > 26 set name=pkg.fmri \
> > > 27
> >
> value=pkg:/web/server/apache-22/module/[email protected]
> > > 28 set name=pkg.renamed value=true
> > > 29 set name=org.opensolaris.consolidation
> value=$(CONSOLIDATION)
> > > 30 depend
> >
> fmri=web/server/apache-22/module/[email protected]
> > \
> > > 31 type=require
> > >
> > > Will I set the version to 0.17.0 just prior to integration or
> > what?
> >
> > I assume that otherwise you get errors about your php packages not
> > being
> > allowed due to userland-incorporation, right? If so, then all you
> > have to
> > do is set the version-locking facets applying to the php packages
> to
> > False.
> > You'd do
> >
> > pkg change-facet facet.version-lock.<pkg-name>=False
> >
> > for each package (you should put them all in the same command,
> since
> > that's
> > a pretty slow command). You might be able to wildcard it somehow
> > (facet.version-lock.web/php*=False or something)
> >
> > > 4) Do I have enough drag forward dependencies to ensure all
> packages
> > update
> > > with pkg update?
> > >
> > > php-52.p5m
> > > 468 # if php apache package present then drag forward
> > > 469 depend \
> > > 470
> >
> fmri=pkg:/web/server/apache-22/module/[email protected],$(BUILD_VERSION)
> > \
> > > 471 type=optional
> >
> > That's kind of a hard question to answer without more information.
> > What
> > are the upgrade scenarios you want to support?
> >
> > Danek
> _______________________________________________
> userland-discuss mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/userland-discuss
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
