On Tue, Aug 26, 2008 at 09:50:33AM -0400, James Carlson wrote: > Anurag S. Maskey writes: > > Because changes from onnv are not merged with the nwam phase 1 gate > > every night, the latest closed sources are not needed. Rather the closed > > sources from the time of merging are needed for nightly builds of the > > phase 1 gate. Thus, the need to maintain closed sources for nwam phase 1. > > I would just keep track of when the merge was last done, and use those > closed binaries when building. > > I don't see a point to keeping closed source around if you're not > actually changing any of it ... but I guess it's your problem to deal > with. > > What exactly are folks outside the firewall supposed to do?
I think that's a good question, and there's probably a way to do this, but I'm too inexperience with the nested repo stuff to have a clue how to do it. I believe the minimum requirement here is an appropriately placed link to the set of closed binaries that match the most recent onnv sync. Is that true? Assuming that's the case, there are two questions: * Where does that link need to be? * How do we map the "node" identifier to the onnv bits the nwam gate is sync'd with? Or I suppose it might work to simply copy over the "latest" tarball at the time of the sync. Should it be copied to usr? usr/closed? Some other location that can be downloaded from? -renee
