On Thu, Feb 3, 2011 at 13:46, Peter Simons <[email protected]> wrote:
> Hi Magnus,
>
>  > [The symlinks] have never disappeared on my system, but then I never
>  > have found a need for them either.
>
> the reason why we need those symlinks is that the repository is served
> to the public being called 'haskell', but we build it under the name of
> 'repo'. Consequently, Pacman expects the repository database to be
> called 'haskell.db.tar.gz' when our users run it, but inside of the
> chroot build, Pacman wants that database to be called 'repo.db.tar.gz'.
>
> The easiest solution I've found to remedy that problem is to create a
> symlink as follows:
>
>  ln -s repo.db.tar.gz haskell.db.tar.gz
>
> That solution is by no means ideal, but it works. Of course, an even
> better solution would be to modify our chroot builds so that they call
> the repository they're building 'haskell' instead of 'repo', then this
> entire problem would just cease to exist. If anyone knows how to
> accomplish that, please share the information!

The easiest solution I found was to never upload the repo.db* files at
all, just the packages, then use ssh to log in and run repo-add on
andromeda.  All of it automated in a script.

/M

-- 
Magnus Therning                      OpenPGP: 0xAB4DFBA4
email: [email protected]   jabber: [email protected]
twitter: magthe               http://therning.org/magnus

_______________________________________________
arch-haskell mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/arch-haskell

Reply via email to