public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Andreas Ziegler <br025@umbiko.net>
To: buildroot@buildroot.org
Cc: Shubham Chakraborty <chakrabortyshubham66@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH] package/pkg-generic: add support for uninstalling packages
Date: Wed, 18 Mar 2026 04:43:54 +0000	[thread overview]
Message-ID: <56f32918983755443d8008e93fd25978@umbiko.net> (raw)
In-Reply-To: <mailman.9.1773748801.2109898.buildroot@buildroot.org>

Hi Thomas, Shubham, ALL,

On 2026-03-17 10:08, Thomas Petazzoni wrote:
> 
> Hello,
> 
> On Tue, Mar 17, 2026 at 01:41:25PM +0530, Shubham Chakraborty wrote:
> 
>> I didn't consider reverse dependencies. The scenario you described
>> (uninstalling openssl breaking ntp) is a
>> serious problem that makes the current implementation unsafe.
>> 
>> I see a few potential approaches to address this:
>> 
>>  1. Add dependency checking that refuses to uninstall if reverse
>> dependencies exist (similar to package managers like apt/dnf)
> 
> This would make the feature useless for a significant number of
> packages I'd say.

In most cases, exactly these reverse dependencies make removal of the 
package desirable. Testing with and without sometimes needs manual 
intervention. Also I prefer clearing up the mess after testing to doing 
a full rebuild: it's less time consuming.

>>  2. Implement cascade uninstall (uninstall the package and all its 
>> reverse
>> dependencies)
> 
> This would probably be the logical thing, I guess?
> 

Nice to have, but is it worth the effort? This is not a tool for 
everyday use, and most people will know what they are doing.

>>  4. Simply document this as a "use at your own risk" feature for 
>> advanced
>> debugging scenarios
>> 
>> I wanted to ask: would any of these approaches be acceptable for 
>> Buildroot?
>> Or is the fundamental issue that without proper
>> dependency tracking during uninstall, this feature is too dangerous to
>> include regardless of warnings/checks?
> 
> This has so far been the project's opinion on this topic. But nothing
> is set in stone forever, so we can always revisit/rediscuss things.

I used to delete files manually, until I discovered the central 
packages-file-list*.txt files, and have been using a similar Python 
script for a few years. Shubham's approach to use the package based 
lists is better.

Including the script as a build target is optional.

> Thomas
> --
> Thomas Petazzoni, co-owner and CEO, Bootlin
> Embedded Linux and Kernel engineering and training
> https://bootlin.com

Kind regards,
Andreas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

       reply	other threads:[~2026-03-18  4:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.9.1773748801.2109898.buildroot@buildroot.org>
2026-03-18  4:43 ` Andreas Ziegler [this message]
2026-03-18  7:44   ` [Buildroot] [PATCH] package/pkg-generic: add support for uninstalling packages Shubham Chakraborty
2026-03-17  7:49 Shubham Chakraborty
2026-03-17  7:58 ` Thomas Petazzoni via buildroot
2026-03-17  8:11   ` Shubham Chakraborty
2026-03-17  9:08     ` Thomas Petazzoni via buildroot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56f32918983755443d8008e93fd25978@umbiko.net \
    --to=br025@umbiko.net \
    --cc=buildroot@buildroot.org \
    --cc=chakrabortyshubham66@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox