Ivan Voras wrote:
2008/7/31 Doug Barton <[EMAIL PROTECTED]>:
As I'm sure you can imagine, I would not regard any solution that
says "portupgrade is mandatory" very favorably, and I don't think
I'd be alone there. What you need to be doing here is to define
the API so that whatever tool(s) the user chooses can interact
with the system.
No, portupgrade isn't mandatory, and it probably never will be
because of ruby. It's only the most widely used and I think that
any scheme that adds or changes to the behaviour of the ports
infrastructure must also include portupgrade to be useful to the
most users.
At first glance these two statements seem contradictory, but I think
what you meant in the second sentence is that for the new system to
work portupgrade has to have support for it before it is rolled out.
If so, then I agree with you and would only add that authors of other
ports management tools should be given adequate notice of the plans as
well.
Note that, if I implement pkg_trans, any tool that doesn't know
about it will, at best, generate useless single-package
transactions (and at worst break the system, but I'll try hard to
avoid this).
Thus my concern. :)
BTW, I thought of another problem scenario. The user installs
port M, and it brings dependencies D1, D2, and D3. Then the user
installs port N which also has port D2 as a dependency.
Port N then won't install D2 as it already exists.
Right, but D2 is still part of the transaction for N. If I roll back M
but leave N installed, then roll back N, D2 should be removed
(assuming for this example that D2 is not relevant to any other port).
The user can rollback [N], then rollback [M+D1+D2+D3]. Trying to
roll back back [M+D1+D2+D3] before [N] will show the user a message
about dependencies.
I seriously doubt that users would put up with that. Trying to think
as a user here, I certainly would not want to be told that in order to
remove a port that I don't want I first have to remove one that I do.
But perhaps I'm misunderstanding you again.
Doug
--
This .signature sanitized for your protection
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
