Shawn Walker wrote:
On Jun 24, 2009, at 4:54 PM, Danek Duvall wrote:
On Wed, Jun 24, 2009 at 04:42:58PM -0500, Shawn Walker wrote:
Of course, right now, the client doesn't handle magically
disappearing packages very well, so a better solution is needed.
I disable and remove depots all the time with no ill effects. Also,
if the
package only disappears to reappear under the aegis of another
publisher,
then will the client handle that any better than one just disappearing?
It is mainly the catalog unexpectedly changing that is the issue.
search, in particular, doesn't like things disappearing from the
catalog and doesn't account for it (currently).
Let's be clear here. On the depot, if you remove packages, use
--rebuild, then copy those directories to another location, start a
different depot with --writable_root pointing to a directory which
already has an index in it, there will be problems. If both depots use
--writable_root and point to the same directory and that directory is
passed, then no problem exists.
In any case, this is a) a bug and one that can be fixed without too much
trouble if there's a compelling to make the above situation work b) has
no relevance to client issues. The client will cope just fine with this
(or at least will break for a different reason) since it uses a
different mechanism to ensure compatibility.
Brock
Removing things from the catalog in the suggested fashion also
eliminates the ability to do incremental updates and wipes out a
repository's updatelog.
You are correct that for installed packages, no ill-effects are likely
to occur other than a user being stuck with an orphaned package that
will not automatically be updated if it appears under the aegis of
another publisher.
Cheers,
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
