Re: [pacman-dev] [PATCH v2] Swap alpm_db_update() implementation to multiplexed version

2020-05-11 Thread Allan McRae
On 12/5/20 12:27 am, guilla...@manjaro.org wrote: > Hi Allan, Hi Anatol, > > I was looking to this new multiplexed implementation and I found some > problems: > 1) This implementation can lead to download databases from different > servers, I think it can't be a problem if they are not synced As

Re: [pacman-dev] [PATCH v2] Swap alpm_db_update() implementation to multiplexed version

2020-05-11 Thread Allan McRae
On 12/5/20 3:14 am, guilla...@manjaro.org wrote: > Le 2020-05-11 17:10, Eli Schwartz a écrit : >> On 5/11/20 10:27 AM, guilla...@manjaro.org wrote: >>> Hi Allan, Hi Anatol, >>> >>> I was looking to this new multiplexed implementation and I found some >>> problems: >>> 1) This implementation can

Re: [pacman-dev] [PATCH v2] Swap alpm_db_update() implementation to multiplexed version

2020-05-11 Thread Anatol Pomozov
Hello Guillaume On Mon, May 11, 2020 at 7:51 AM wrote: > > Hi Allan, Hi Anatol, > > I was looking to this new multiplexed implementation and I found some > problems: > 1) This implementation can lead to download databases from different > servers, I think it can't be a problem if they are not

Re: [pacman-dev] [PATCH v2] Swap alpm_db_update() implementation to multiplexed version

2020-05-11 Thread Eli Schwartz
On 5/11/20 10:27 AM, guilla...@manjaro.org wrote: > Hi Allan, Hi Anatol, > > I was looking to this new multiplexed implementation and I found some > problems: > 1) This implementation can lead to download databases from different > servers, I think it can't be a problem if they are not synced

Re: [pacman-dev] [PATCH v2] Swap alpm_db_update() implementation to multiplexed version

2020-05-11 Thread guillaume
Hi Allan, Hi Anatol, I was looking to this new multiplexed implementation and I found some problems: 1) This implementation can lead to download databases from different servers, I think it can't be a problem if they are not synced 2) Differents download payloads are created for databases and

Re: [pacman-dev] [PATCH v2] Swap alpm_db_update() implementation to multiplexed version

2020-05-07 Thread Allan McRae
On 7/5/20 6:01 pm, Allan McRae wrote: > On 7/5/20 11:49 am, Anatol Pomozov wrote: >> Now when all callers of the old alpm_db_update() function are gone we can >> remove this implementation. And then rename alpm_dbs_update() function to >> alpm_db_update(). >> >> Signed-off-by: Anatol Pomozov >>

Re: [pacman-dev] [PATCH v2] Swap alpm_db_update() implementation to multiplexed version

2020-05-07 Thread Allan McRae
On 7/5/20 11:49 am, Anatol Pomozov wrote: > Now when all callers of the old alpm_db_update() function are gone we can > remove this implementation. And then rename alpm_dbs_update() function to > alpm_db_update(). > > Signed-off-by: Anatol Pomozov > --- ../src/pacman/util.c: In function

Re: [pacman-dev] [PATCH v2] Swap alpm_db_update() implementation to multiplexed version

2020-05-06 Thread Allan McRae
On 7/5/20 11:49 am, Anatol Pomozov wrote: > Now when all callers of the old alpm_db_update() function are gone we can > remove this implementation. And then rename alpm_dbs_update() function to > alpm_db_update(). > > Signed-off-by: Anatol Pomozov > --- Thanks. Also good to have the README

[pacman-dev] [PATCH v2] Swap alpm_db_update() implementation to multiplexed version

2020-05-06 Thread Anatol Pomozov
Now when all callers of the old alpm_db_update() function are gone we can remove this implementation. And then rename alpm_dbs_update() function to alpm_db_update(). Signed-off-by: Anatol Pomozov --- README| 3 + lib/libalpm/alpm.h| 40 +- lib/libalpm/be_sync.c |