On Sun, May 16, 2010 at 6:47 PM, Akshat Kumar
wrote:
> On 5/16/10, ron minnich wrote:
>> Between this package tool and mercurial for sources, I don't expect to
>> ever need to run replica again.
>
> How do you plan to keep up with updates
> to contrib repos people keep on sources?
the BUILD tool
On 5/16/10, ron minnich wrote:
> Between this package tool and mercurial for sources, I don't expect to
> ever need to run replica again.
How do you plan to keep up with updates
to contrib repos people keep on sources?
Will the contrib -> iso.bz2 conversion take
place on a nightly basis? Some sor
OK I double-checked and the 'install' script does indeed create
/installed/package-name.
So, if you have bound something onto /installed, or the directory
exists, you should be fine.
fgb has suggested improvements to my BUILD script, which I will put in
this week.
Any other suggestions are most
On Sat, May 15, 2010 at 7:56 PM, Federico G. Benavento
wrote:
> hmm... this looks good, you are still using the .iso's
> from the existing packages.
not quite. I actually recreate all the .iso's from the proto files in
replica//proto.
The reason is that in some cases, the root/ directories for s
hmm... this looks good, you are still using the .iso's
from the existing packages.
using hget makes it faster of course, you could
hget from http://plan9.bell-labs.com/sources/contrib
but that would mean the user/package thing...
centralization sometimes makes things easier.
kudos
On Sat, May 15
Here is a refinement of fgb's fine work on a contrib system. I have
taken his ideas a bit further, based on my use of his tools in an
unreliable environment. I was getting quite frustrated as I had
multiple failures in the midst of an install, and seeing the message
'xyz already installed', when it
