Message-ID: <38a90a9a-644b-0d99-ec2d-71c8ba48ec54@gmail.com>
Date: Sat, 21 Jan 2023 15:22:03 +0530
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.4.2
Reply-To: vkrishn4@gmail.com
Subject: Re: suggesting feature, splitting pkgs repositories (part II)
To: Timo Teras <timo.teras@iki.fi>
References: <3535e75e-f682-7435-a1f4-cd6d38180cfc@gmail.com>
 <Y8mkqZZDcmOQGYZQ@7a0aac3667e2> <20230121095717.2f489602@onyx.my.domain>
Content-Language: en-US
From: "V.Krishn" <vkrishn4@gmail.com>
Organization: Insteps.net
Cc: ~alpine/devel@lists.alpinelinux.org
In-Reply-To: <20230121095717.2f489602@onyx.my.domain>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 1/21/23 13:27, Timo Teras wrote:
> On Thu, 19 Jan 2023 20:14:33 +0000
> Kevin Daudt <kdaudt@alpinelinux.org> wrote:
> 
>> On Thu, Jan 19, 2023 at 11:08:31PM +0530, V.Krishn wrote:
>>>
>>> Would like to suggest moving -dbg pkgs in repositories into a
>>> separate folder. eg.
>>> main/aarch64.dbg or community/aarch64.dbg/
> 
> This is not possible with changing apk code.
> 
>>> OR
>>> main.dbg/aarch64 or community.dbg/aarch64
> 
> This or some similar option like main-dbg, or dbg/main would be
> possible without touch apk code.
> 
>>> Suggested change is desirable because:
>>> 1. Users who would want to install -dbg pkgs are willing to do
>>> debugging. They are mostly development oriented.
> 
> This would mean that new repositories need to be added if user wants to

If user are installing -dbg pkgs, it can be expected to know things 
around apk, /etc/apk/.. and the ability to add a line or two in 
/etc/apk/repositories

> use debug packages. Or perhaps adding some new apk feature to make
> enablign the debug repos possible some other way.

Making it simple is always welcomed, but that would first need 
formalizing on variables like repo path .. etc. Maybe modifying apk 
could wait.

> 
>>> 2. Mirrors may opt to ignore these .dbg folder, thereby saving some
>>> disk space.
> 
> Understand. These can be fairly large at times. And it would be also
> possible to configure close mirror without -dbg and another mirror with
> the -dbg packages.
> 
> As an additional benefit the repository indexes without dbg packages
> would be smaller - possibly helping embedded systems.

Already happening.

  And as mentioned
> allow perhaps turning -dbg on by default (assuming we have enough disk
> space on main mirrors).
> 
>> The question is if it is possible to move subpackages to a different
>> repository as the origin package.
> 
>  From apk-tools side there is no problem. Having subpackages in a
> separate repo is perfectly ok.
> 
> The complication comes from the building side. It would need special
> logic to move the -dbg pacakges to different repository. And changes to
> rebuild multiple indexes, and uploading to right place.
> 
> abuild also has assumptions that all generated packages are in same
> destionation. This applies to detecting whether a rebuild is needed,
> and on removing obsoleted packages.
> 
> All of the above should be doable, but might be non-trivial in some
> cases.
> 
> I think the idea is good. But am not sure if/when someone would have
> time to work on it. Would someone be willing to do the work if no one
> objects for the change?

Thanks for clarifications.
Looking forward in positive way :)

> 
> Timo

-- 
Regards,
V.Krishn