Thanks, that answers my main question. How are the consolidations going
to be informed/educated? We do have gatekeeper mailing lists set up, if
Also, I am not sure if you are aware, but there are different practices
already among consolidations with regard to what they deliver. The
Desktop consolidation, for example, already practices what this tool
would help with, and only creates new versions of packages that actually
do have content change. ON, on the other hand, has always had the policy
of delivering everything even if only a single package changes.
On 08/15/13 11:42 AM, Erik Trauschke wrote:
On 08/15/13 11:17 AM, Alan Steinberg wrote:
This does sound very useful in a general sense, but I do not know what
Erik originally meant by "aka new publication deployment model". Will it
affect how consolidations create their repos for delivery to the WOS?
Does it affect what RE does in processing the C-team repo packages?
The original plan, before anyone started to look closely at the
problem, was to change pkgsend to only publish a new version if it
actually does have a content change to the latest version already in
the repo. After a bunch of discussion this was deemed unfeasible,
mainly due to the problem that packages might be unchanged for one
variant but not an other.
We decided to provide a separate tool instead, which will resurface
the repo based on a package list of a reference repo.
The vision for this tool is the following:
Consolidations will create their repositories the same way they always
have. But before they provide the repo to RE for assembling the WOS
(as well as providing the repo as a nightly pkg source), they will run
pkgsurf to prune out any superfluous packages (i.e. unchanged packages).
For now we will let consolidations experiment with pkgsurf, but at
some point we will probably require consolidations to run it before
delivering their repo.
RE should actually not be required to run the tool at all. However, it
might be a good practice to run pkgsurf in noexecute mode to check if
it actually finds differences between the last WOS build and the
I hope I could clarify what the intent for pkgsurf is. Let me know if
you have any additional questions.
On 08/ 9/13 06:32 PM, B.J. Wahl wrote:
Fantastic!! Thanks for getting this done.
Sent from my iPhone
On Aug 9, 2013, at 6:04 PM, Erik Trauschke
Author: Erik Trauschke
Latest revision: 71a6862183d8e9e14e7393b20fa2ccea0c2bea09
16992741 New publication tool, which reverts pkgs in repo if content
17295321 FactoredManifest stores incomplete manifest to disk
[pkg-discuss] Re: 16992741 New publication tool, which reverts pkgs in repo if content hasn't changed