[email protected] wrote:
- Should I copy every import file I modify into the 127 directory, or
modify them where they are? David?
Given that we're only talking about metadata here which otherwise will
be ignored, I'm alright with modifying the most recent version of each
in-place import files (we haven't always been consistent here, or
perhaps we've applied our own consistency rules!)
Great, thanks!
- I'd like these to be installed by default. I can either do an (I'm
guessing) install gate putback. Or, I can wait until the sat solver
wad gives me nested incorporations and have entire drag them in. If I
wait, the on repo users will have to manually install them all in the
meantime, which might be ok, though a bit annoying. Opinions?
Don't we need to wait for the SAT solver in any case since in the
upgrade case "entire" would be replaced by the nested incorporation?
Or am I missing something here?
You have a good point, and I'll plan to integrate without the new
incorporations being installed by default, with the intent that this will
be fixed once we have the SAT solver and I can redefine entire as simply
including the other incorporations.
But I'm not sure if we were speaking past each other, so I'll attempt to
be complete below. :)
Right now, I intend to deliver an incorporation per consolidation *plus*
an "entire" incorporation that was defined as it always was, as a set of
direct dependencies on the packages it incorporates. I'm not currently
changing the way entire was delivered -- I'm just delivering additional
incorporations.
It would be nice if they were installed by default. There are 2 ways to
do that:
1) Define entire as depending on the consolidation incorporations, rather
than specifying the package dependencies directly. That's the eventual
goal, but not possible until the sat solver wad.
2) Modify the installers (the DC manifests) to include these
incorporations as part of their default package set, just like they do
entire. (As you mention above, this doesn't handle the upgrade case.)
Right now the ON repo redefines entire to be *only* the ON packages.
That's very very bad, and I need to change it ASAP. (A number of upgrade
scenarios are near impossible.) So, as soon as 127 is available in /dev,
I'll change the ON repo to not redefine entire, and only deliver the ON
incorporation.
If the consolidation incorporations aren't installed by default, a
developer will need to first pkg install the consolidation incorporations,
and then uninstall entire to allow the consolidations to move
independently. If they are, the new instructions will just be to
uninstall entire.
But, you're absolutely right that adding the new packages to the installer
doesn't mean they'll get installed on upgrade. So, I'll skip modifying
the installer and just look forward to updating 'entire' later so the new
incorporations will get brought in as dependencies of 'entire'.
(I still have testing to do to make sure this will all work as I expect,
but I just wanted to make sure my plan was solid before investing in
extensive testing.)
liane
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
