On 25/11/13 17:15, Sam Stuewe wrote:
One question needs answered first. Should there be able to be two different mirror arrays. I.e. If a PKGBUILD has multiple source files available across mirrors, will those be the same mirrors? Though I think the flexibility of having an option for multiple source files to have mirrored sources, I agree that the number of use cases is
If the answer is no, we can simplify this some more to:
source=('mirror://foo/foo.tar.xz') mirror=('http://bar.com/download' 'http://baz.com/mirror/download') I do love how simple that would be. If the end result of this proposal is this simple solution, or one slightly more complex one that supports multiple sources with mirrors, I will be satisfied either way. The only extra argument I would make in favor of supporting multiple mirrored
On 2013-11-24 23:46, Allan McRae wrote: probably very small. sources is that it seems odd to allow a special case only for one source file. Wouldn't it be more less hacky and more standardized if PKGBUILDs treated source files as equal?
I'm fairly certain the number of PKGBUILDs that have source files that are mirrored in different locations can be well approximated by zero. I'm not even sure the mirror feature will get a lot of use, given many (most?) places that provide mirrors of their files set up a round robin or geolocation to balance the load across mirrors anyway. I know there are obvious exceptions to that, so I am happy adding mirror support. Someone would have to convince me that adding more than one source mirror array would be a useful prospect. Allan