Re: trimming changelogs

2020-03-29 Thread Guillem Jover
Hi! On Fri, 2020-03-20 at 00:50:29 +0100, Adam Borowski wrote: > In the rush for cutting away small bits of minbase, it looks like we forgot > a big pile of junk: /usr/share/doc/ As has been mentioned on the thread, this is IMO a non-issue, as these pathnames can be trimmed automatically with

Re: installing minimal systems with weeed out /u/s/d (was: trimming changelogs)

2020-03-22 Thread Johannes Schauer
Hi, Quoting Marc Haber (2020-03-22 12:20:37) > On Fri, 20 Mar 2020 10:16:00 +0100, David Kalnischkies > wrote: > >On Fri, Mar 20, 2020 at 12:50:29AM +0100, Adam Borowski wrote: > >> In the rush for cutting away small bits of minbase, it looks like we forgot > >> a big pile of junk:

installing minimal systems with weeed out /u/s/d (was: trimming changelogs)

2020-03-22 Thread Marc Haber
On Fri, 20 Mar 2020 10:16:00 +0100, David Kalnischkies wrote: >On Fri, Mar 20, 2020 at 12:50:29AM +0100, Adam Borowski wrote: >> In the rush for cutting away small bits of minbase, it looks like we forgot >> a big pile of junk: /usr/share/doc/ > >Honestly, on space constraint systems, isn't the

Re: trimming changelogs

2020-03-20 Thread Johannes Schauer
Hi, Quoting Mo Zhou (2020-03-20 16:07:04) > That said, I agree that we move a step further considering a slim base system > in a more constructive way. Spontaneously, I'd raise such a question: Is the > changelogs the only files to blame for the waste of precious space? Some > packages contains

Re: trimming changelogs

2020-03-20 Thread Mo Zhou
Hi Adam, Thank you for putting this forward, but actually I'm personally object to trimming changlogs from a normal[1] system. A complete changelog helps me quickly understand what happened to the component of the package. Once trimmed, such changelog get crippled. Why not directly keep only the

Re: trimming changelogs

2020-03-20 Thread Ole Streicher
Julien Puydt writes: > Le vendredi 20 mars 2020 à 07:44 +0100, Ansgar a écrit : >> We should probably also not ship the same changelog in multiple >> packages, especially when one depends on the other. > > Switching to per src:package changelogs would cover that. This would be useful for the

Re: trimming changelogs

2020-03-20 Thread David Kalnischkies
On Fri, Mar 20, 2020 at 12:50:29AM +0100, Adam Borowski wrote: > In the rush for cutting away small bits of minbase, it looks like we forgot > a big pile of junk: /usr/share/doc/ Honestly, on space constraint systems, isn't the whole /usr/share/doc directory "junk". Probably not the solution for

Re: trimming changelogs

2020-03-20 Thread Paul Wise
On Fri, Mar 20, 2020 at 8:56 AM Tomas Pospisek wrote: > I don't know man minbase is, so I don't know what you are > talking about. The debootstrap variant option minbase: https://manpages.debian.org/buster/debootstrap/debootstrap.8.en.html#OPTIONS "minbase, which only includes required

Re: trimming changelogs

2020-03-20 Thread Tomas Pospisek
On 20.03.20 00:50, Adam Borowski wrote: > In the rush for cutting away small bits of minbase [...] > [trim changelogs] I don't know man minbase is, so I don't know what you are talking about. On a normal desktop/server I'd expect /usr/share/doc/$PKG/changelog.Debian* to contain the whole

Re: trimming changelogs

2020-03-20 Thread Julien Puydt
Hi, Le vendredi 20 mars 2020 à 07:44 +0100, Ansgar a écrit : > > We should probably also not ship the same changelog in multiple > packages, especially when one depends on the other. > Switching to per src:package changelogs would cover that. But that will probably mean making dpkg smarter.

Re: trimming changelogs

2020-03-20 Thread Samuel Thibault
Hello, Boyuan Yang, le jeu. 19 mars 2020 20:58:57 -0400, a ecrit: > Maybe we can keep changelog of up to 10 entries or till the time of 5 years > ago As a user, I would like to see changelog until at least the previous Debian release, to be able to grep through it for changes when I happend to

Re: trimming changelogs

2020-03-20 Thread Ansgar
Hi, Adam Borowski writes: > Of files named changelog.*, top offenders are: [ Trimmed list to duplicates ] > 223009 ncurses-bin:changelog.gz > 223009 ncurses-base:changelog.gz > 223009 libtinfo6:changelog.gz > 210621 libc6:changelog.Debian.gz > 210621 libc-bin:changelog.Debian.gz > 145889

Re: trimming changelogs

2020-03-19 Thread Adam Borowski
On Thu, Mar 19, 2020 at 08:58:57PM -0400, Boyuan Yang wrote: > 在 2020-03-20星期五的 00:50 +0100,Adam Borowski写道: > > [trimming changelogs] > > > > On the other hand, changelogs are valuable. Unlike some folks on IRC > > I wouldn't want to tightly trim al

Re: trimming changelogs

2020-03-19 Thread Boyuan Yang
Hi, 在 2020-03-20星期五的 00:50 +0100,Adam Borowski写道: > Hi! > In the rush for cutting away small bits of minbase, it looks like we forgot > a big pile of junk: /usr/share/doc/ > [...] > Seems like a tempting area to trim... > [...] > Ubuntu keep only 10 last entries, for _all_ packages. > > I

trimming changelogs

2020-03-19 Thread Adam Borowski
Hi! In the rush for cutting away small bits of minbase, it looks like we forgot a big pile of junk: /usr/share/doc/ On strict minbase (rather than prio:important which really matters), the docs take 11MB. And of that, 8MB are files named changelog.* -- which fails to include eg. bash's: 112K