On 03/13/12 10:49, Shawn Walker wrote:
[snip]
[snip]
6) For all depend actions in manifests to be published which use
<pkg-name>@current in the target or predicate, if <pkg-name> is in the
set of "different manifests", replace @current with the version of the
package in the package to be published, otherwise replace @current
with
the version of the previously published manifest
How will you deal with timestamps which are server side, or is your
assumption that @current doesn't include the timestamp?
@current is literally the magical string "@current", there is no
timestamp.
You misunderstand me. I was referring to "replace @current with the
version of the package in the package to be published", etc. When the
replacement is done, does that replacement include the timestamp?
Since automatically generated dependencies don't include timestamps now,
I can't see why we'd start adding them to the versions that replace
@current. That does mean that there's a shortcut we can take where if
the currently published package and the package to be published have the
same version, then we know what version to replace @current with before
we even do the manifest diffs.
Brock
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
