[arch-general] custom repo guide?
Hey, can you link me to a manual on custom repositories? I couldn't find anything on the wiki. Specifically what needs to be done on the server side to maintain the package index. Looks like that is all that's needed for a repo, is it? thanks. -- Arvid Asgaard Technologies
Arvid Picciani wrote:
Hey,
can you link me to a manual on custom repositories? I couldn't find anything on the wiki. Specifically what needs to be done on the server side to maintain the package index.
Looks like that is all that's needed for a repo, is it?
thanks.
http://wiki.archlinux.org/index.php/Custom_local_repository_with_ABS_and_gen...
Allan McRae wrote:
Arvid Picciani wrote:
Hey,
can you link me to a manual on custom repositories? I couldn't find anything on the wiki. Specifically what needs to be done on the server side to maintain the package index.
Looks like that is all that's needed for a repo, is it?
thanks.
http://wiki.archlinux.org/index.php/Custom_local_repository_with_ABS_and_gen...
cake! thanks. any idea how to build packages for a repo in bulk though? preferable even with more generic make options then my workstation would have. -- Arvid Asgaard Technologies
On Wed, Dec 2, 2009 at 12:01 PM, Arvid Picciani <aep@exys.org> wrote:
Allan McRae wrote:
Arvid Picciani wrote:
Hey,
can you link me to a manual on custom repositories? I couldn't find anything on the wiki. Specifically what needs to be done on the server side to maintain the package index.
Looks like that is all that's needed for a repo, is it?
thanks.
http://wiki.archlinux.org/index.php/Custom_local_repository_with_ABS_and_gen...
cake! thanks.
any idea how to build packages for a repo in bulk though? preferable even with more generic make options then my workstation would have.
You know, I tried making a script to do this and it ended up going no where. The intent was to use makechrootpkg (from devtools) to build packages in a chroot and consequently install the package to the chroot when completed. The only stipulation was that you needed to manually specify the build order and do the dep stuff manually. I'd suggest making a dumb script to just call makechrootpkg repeatedly. If you're doing deps, then order matters, if not, then a simple loop like so would work: for pkg in pkgbuilds/*; do pushd "$pkg" makechrootpkg -c /path/to/chroot #or whatever popd done
On Wed, Dec 2, 2009 at 13:17, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
The only stipulation was that you needed to manually specify the build order and do the dep stuff manually.
Maybe you could use pactree for this, to generate the order somehow? It seems like it's possible to do, except for any dep cycles.
Daenyth Blank wrote:
On Wed, Dec 2, 2009 at 13:17, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
The only stipulation was that you needed to manually specify the build order and do the dep stuff manually.
Maybe you could use pactree for this, to generate the order somehow? It seems like it's possible to do, except for any dep cycles.
I started a script: http://allanmcrae.com/scripts/rebuildorder it is a bit crap and does not deal with makedeps...
Aaron Griffin wrote:
You know, I tried making a script to do this and it ended up going no where. The intent was to use makechrootpkg (from devtools) to build packages in a chroot and consequently install the package to the chroot when completed. The only stipulation was that you needed to manually specify the build order and do the dep stuff manually.
I'd suggest making a dumb script to just call makechrootpkg repeatedly. If you're doing deps, then order matters, if not, then a simple loop like so would work: for pkg in pkgbuilds/*; do pushd "$pkg" makechrootpkg -c /path/to/chroot #or whatever popd done
Nice. mkchrootpkg appears to be exactly what i need. I'm going to do that, thanks. I guess i have it a little easier with the dependencies, since i can pull almost all of them from upstream binaries. -- Arvid Asgaard Technologies
participants (4)
-
Aaron Griffin
-
Allan McRae
-
Arvid Picciani
-
Daenyth Blank