[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [PATCH 6/6] Before resolve dependencies, add all packages listed on the task



Steve McIntyre <steve@einval.com> writes:

> On Tue, Feb 06, 2007 at 08:45:37AM -0200, Otavio Salvador wrote:
>>From: Otavio Salvador <otavio@ossystems.com.br>
>>
>>Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
>
> Hmmm. I'm not convinced by this one, either. It's a major decision to
> change dependency ordering, and we expect dependency resolution to
> work. What's the point of including packages in a task before all the
> dependencies?

Current code do not check the prefered packages of task before adding
a dependency so, for example:

A task having:

packageA
packageB

And the packages having:

packageA depends packageC | packageB
packageB

Will result in:

packageA
packageC
packageB

After this patch, you'll end with:

packageA
packageB

This can lead to a high size reduction on the produced CD and also
makes sense since the packages on the list has preference to be
include on the disc. That's why.

-- 
Otavio Salvador                  O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854         http://projetos.ossystems.com.br



Reply to: