[arch-releng] our core-dual images are too big

Pierre Schmitz pierre at archlinux.de
Mon May 16 00:30:06 EDT 2011

On Sun, 15 May 2011 12:25:18 +0200, Dieter Plaetinck wrote:
> On Fri, 06 May 2011 15:28:29 +0200
> Pierre Schmitz <pierre at archlinux.de> wrote:
>> On Fri, 06 May 2011 17:45:13 +1000, Allan McRae wrote:
>> > On 06/05/11 17:31, Dieter Plaetinck wrote:
>> >> On Thu, 05 May 2011 21:38:14 -0300
>> >> adding exceptions in download-repo.sh to work around limitations in our
>> >> repo scripts is not the way to go imho.  let's get those packages out
>> >> of core the proper way, and let's see if/how we can cut another 10MB.
>> >>
>> >
>> > That limitation in the devtools/db-scripts has been around ever since
>> > split packages became available in pacman/makepkg.   I would not bank
>> > on it getting fixed in the short term  (or even in the long term...)
>> I wont got into details here but putting split packages into different
>> repos is a "wont implement". It's more a limitation of how we use svn
>> and the repos. There was a thread about the details on the mailing list.
> I can't find that thread. Where exactly was this discussed?
> I understand this is probably hard to fix, on the other hand:
> 1) this is a violation of what the core repository is for (and we had a very
> extensive discussion on that recently). see
> https://wiki.archlinux.org/index.php/Official_repositories#.5Bcore.5D
> 2) it makes the core repo bigger than it should be, which makes my
> job harder.
> Dieter

I have to admit my response as probably too short. The thread I meant
and some other related ones which I didn't find quickly.

The problem is how we store PKGBUILDs in svn and assign them to
different repos and arches. (e.g. /pkgname/repos/extra-i686) This
wont work with several use cases we'd like to have: split packages with
different architectures and repositories. Later in that thread I have
proposed a possible solution. But I haven't a solid concept yet and it
will be a major break and would probably need changes in makepkg etc..

In short: There is no simple patch to solve this as this us an design
issue. Trying to add it to our current repo layout would be an ugly
hack, complex and in fact this would be a bigger violation of our

However: I know about these issue and they will probably solved in some
way in the future. But you shouldn't wait for it to happen.



Pierre Schmitz, https://users.archlinux.de/~pierre

More information about the arch-releng mailing list