[arch-multilib] Developer tools
Hello, Are we planning any modifications to devtools to take into account the new repo ? I am volunteer to help packaging gtk2 and its dependencies, for example.
On 08/25/2010 06:48 PM, Rémy Oudompheng wrote:
Hello,
Are we planning any modifications to devtools to take into account the new repo ? I am volunteer to help packaging gtk2 and its dependencies, for example.
devtools has support for the new repo in git. http://projects.archlinux.org/dbscripts.git/log/ -- Ionuț
On 2010/8/25, Ionuț Bîru <ibiru@archlinux.org> wrote:
devtools has support for the new repo in git.
May I suggest the following changes ? They make more sense for using multilib-build. For example, packages from [multilib] should be installed when available, not packages from [community] (multilib must come first in pacman.conf). -- Rémy
On Wed, Aug 25, 2010 at 7:13 PM, Rémy Oudompheng <remyoudompheng@gmail.com> wrote:
May I suggest the following changes ? They make more sense for using multilib-build. For example, packages from [multilib] should be installed when available, not packages from [community] (multilib must come first in pacman.conf).
I already talked to Pierre about this. Should be irrelevant, since there's no intersection between [community] and [multilib] (once we remove the lib32 stuff from [community]. gcc-multilib should of course be installed into the multilib root. I support that. :)
On Wed, 25 Aug 2010 22:56:33 +0200, Jan Steffens <jan.steffens@gmail.com> wrote:
On Wed, Aug 25, 2010 at 7:13 PM, Rémy Oudompheng <remyoudompheng@gmail.com> wrote:
May I suggest the following changes ? They make more sense for using multilib-build. For example, packages from [multilib] should be installed when available, not packages from [community] (multilib must come first in pacman.conf).
I already talked to Pierre about this. Should be irrelevant, since there's no intersection between [community] and [multilib] (once we remove the lib32 stuff from [community].
gcc-multilib should of course be installed into the multilib root. I support that. :)
I'll release a new devtools package soon. If your package needs the multilib gcc to be build it should be put into makedepends. (Or create a group like base-devel-multilib which I could install into the chroot in addition to base and base-devel; though I don't know if pacman can handle the conflict between gcc and gcc-multilib. -- Pierre Schmitz, https://users.archlinux.de/~pierre
Pierre Schmitz <pierre@archlinux.de> wrote:
I'll release a new devtools package soon. If your package needs the multilib gcc to be build it should be put into makedepends. (Or create a group like base-devel-multilib which I could install into the chroot in addition to base and base-devel; though I don't know if pacman can handle the conflict between gcc and gcc-multilib.
archbuild with the patch I posted earlier works fine for me. -- Rémy
participants (4)
-
Ionuț Bîru
-
Jan Steffens
-
Pierre Schmitz
-
Rémy Oudompheng