INFO: cvs downtime

[Elan Ruusamäe]

On Wednesday 29 April 2009 10:53:01 Tomasz Pala wrote:
> On Wed, Apr 29, 2009 at 09:45:44 +0200, Arkadiusz Miskiewicz wrote:
> >> And how about moving scripts (builder, adapter etc.)? It would be
> >> finally possible 'to bring them all and in the darkness bind them'.
> >
> > I like doing just ../builder -bb whatever or ../pldnotify.awk
> > package/package.spec but well. Better solutions are welcome.
>
> I like it too (well, with one leading dot ;>) - you could keep this on
> client-side many ways:
> - symlink to packages,
> - symlink to ~/bin,
> - creating alias
> or via symlinks on server-side - but IMHO it's better to leave this for
> user (I'd symlink only scripts I use).

how about (for now) just /packages as files? as it would be easier to locate 
them (builder --init-rpm-dir would checkout them for you)

later we could improve ./builder script to always create the ./symlinks to 
tools dir?

in long term all those should go to rpm-build-macros package perhaps (and 
rpm-build-macros be renamed to rpm-build-tools?) so you could grab them 
from /usr/share/blah without network access (install from rpm)

-- 
glen