Warren Togami wrote:
> Hans de Goede wrote:
>>
>> I think we need to think this one over a bit more. For now I'm just
>> going along with raidem-music with %{?dist}, I want to get that of my
>> todo list. Then we can take our time to come up with something sane for
>> this.
>>
>> We might as well include packages in the discussion were upstream
>> doesn't split content and engine and we want to split these.
>>
>
> For the noarch data package that is the same in content between dists,
> go ahead and go distless for now. Send me requests directly, and I will
> *copy* the entire signed package from one dist tree to another. So you
> build it once and it will be replicated. We will need to formalize this
> process sometime later.
>
Okay, sounds good, so I basicly only keep a devel branch (no use for
other identical branches then I guess, especially since I cannot tag
them), build that and ask you to the result over to FC-5 (and possible
others, but in this case only FC-5).
Wouldn't it be a good idea to use symlinks for this then, or can't the
mirrors handle this? With symlinks we would get a real save in diskspace
and bandwidth (only mirroring bandwidth, but still). The same (symlinks)
can be argued for the i386 packages currently copied into the x86_64 repo.
Regards,
Hans
