Re: Planned setup.ini changes for early 2018

2019-05-30 Thread Jon Turney
On 01/03/2018 16:00, Jon Turney wrote: On 10/01/2018 22:44, Jon Turney wrote: * Migrate from setup.hint to pvr.hint in release area I also plan to migrate all remaining setup.hints to pvr.hints in the release area (setup.hint in uploads have been automatically migrated since [5]). This

Re: Planned setup.ini changes for early 2018

2018-03-01 Thread Jon Turney
On 01/03/2018 16:39, Marco Atzeri wrote: On 01/03/2018 17:00, Jon Turney wrote: I've done this migration today. Have you stopped calm schedule ? It seem not reactive calm was stopped between 02:00 and 15:45 UTC today. Your postgres upload has been processed, but no email was sent

Re: Planned setup.ini changes for early 2018

2018-03-01 Thread Marco Atzeri
On 01/03/2018 17:00, Jon Turney wrote: I've done this migration today. Have you stopped calm schedule ? It seem not reactive

Re: Planned setup.ini changes for early 2018

2018-03-01 Thread Jon Turney
On 10/01/2018 22:44, Jon Turney wrote: * Migrate from setup.hint to pvr.hint in release area I also plan to migrate all remaining setup.hints to pvr.hints in the release area (setup.hint in uploads have been automatically migrated since [5]). This should have no effect on the generated

Re: Planned setup.ini changes for early 2018

2018-01-28 Thread Jon Turney
On 22/01/2018 23:13, Jon Turney wrote: On 10/01/2018 22:44, Jon Turney wrote: * Add depends: to version descriptions This is a version-specific list of required packages (as opposed to requires:, which is per-package, and contains the union of the dependencies for all versions). I believe

Re: Planned setup.ini changes for early 2018

2018-01-24 Thread Achim Gratz
Jon Turney writes: > I considered a few approaches, including what you suggest. > > This approach is more work, and a lot of churn, in both setup and > calm. The only additional benefit you've identified is removing > clutter. Well, it'd give you a clean slate to start from and the transformation

Re: Planned setup.ini changes for early 2018

2018-01-16 Thread Achim Gratz
Jon Turney writes: > The purpose of my original email is to start that discussion. Well, sorry then for not recognizing that, but from your other answers in this thread I've got the impression src/ is a done deal that you didn't want to discuss. > If I've understood correctly, your objection is

Re: Planned setup.ini changes for early 2018

2018-01-15 Thread Jon Turney
On 13/01/2018 18:35, Achim Gratz wrote: Jon Turney writes: * De-duplicate source archives Source archives which are identical[2] between x86 and x86_64 will be moved to paths starting src/ in the release area. You keep acting like using a new src/ hierarchy was already decided upon, yet I

Re: Planned setup.ini changes for early 2018

2018-01-13 Thread Achim Gratz
Achim Gratz writes: > Put these in noarch/ and arrange for setup to be able to install both > from noarch/ and $arch/ so that we can also de-duplicate things like > debuginfo and documentation down the road. I forgot to add that this is already possible by injecting extra packages: say you

Re: Planned setup.ini changes for early 2018

2018-01-13 Thread Achim Gratz
Jon Turney writes: > * De-duplicate source archives > > Source archives which are identical[2] between x86 and x86_64 will be > moved to paths starting src/ in the release area. You keep acting like using a new src/ hierarchy was already decided upon, yet I don't remember it even getting

Re: Planned setup.ini changes for early 2018

2018-01-13 Thread Jon Turney
On 12/01/2018 18:11, Peter A. Castro wrote: On Fri, 12 Jan 2018, Jon Turney wrote: On 11/01/2018 17:53, Peter A. Castro wrote: On Wed, 10 Jan 2018, Jon Turney wrote: * Add depends: to version descriptions This is a version-specific list of required packages (as opposed to requires:, which

Re: Planned setup.ini changes for early 2018

2018-01-13 Thread Jon Turney
On 10/01/2018 23:27, David Stacey wrote: On 10/01/18 22:44, Jon Turney wrote: * Add depends: to version descriptions * De-duplicate source archives * Migrate from setup.hint to pvr.hint in release area That all sounds good to me. Regarding the de-duplication of source files: will sources

Re: Planned setup.ini changes for early 2018

2018-01-12 Thread Peter A. Castro
On Fri, 12 Jan 2018, Jon Turney wrote: On 11/01/2018 17:53, Peter A. Castro wrote: On Wed, 10 Jan 2018, Jon Turney wrote: * Add depends: to version descriptions This is a version-specific list of required packages (as opposed to requires:, which is per-package, and contains the union of the

Re: Planned setup.ini changes for early 2018

2018-01-12 Thread Jon Turney
On 11/01/2018 17:53, Peter A. Castro wrote: On Wed, 10 Jan 2018, Jon Turney wrote: * Add depends: to version descriptions This is a version-specific list of required packages (as opposed to requires:, which is per-package, and contains the union of the dependencies for all versions). I

Re: Planned setup.ini changes for early 2018

2018-01-11 Thread Achim Gratz
Jon Turney writes: > * Add depends: to version descriptions > > This is a version-specific list of required packages (as opposed to > requires:, which is per-package, and contains the union of the > dependencies for all versions). > > I believe that historical setup versions will either ignore, or

Re: Planned setup.ini changes for early 2018

2018-01-11 Thread Peter A. Castro
On Wed, 10 Jan 2018, Jon Turney wrote: Greetings, Jon, * Add depends: to version descriptions This is a version-specific list of required packages (as opposed to requires:, which is per-package, and contains the union of the dependencies for all versions). I believe that historical setup

Re: Planned setup.ini changes for early 2018

2018-01-10 Thread David Stacey
On 10/01/18 22:44, Jon Turney wrote: * Add depends: to version descriptions * De-duplicate source archives * Migrate from setup.hint to pvr.hint in release area That all sounds good to me. Regarding the de-duplication of source files: will sources for 'noarch' packages remain in 'noarch',

Planned setup.ini changes for early 2018

2018-01-10 Thread Jon Turney
* Add depends: to version descriptions This is a version-specific list of required packages (as opposed to requires:, which is per-package, and contains the union of the dependencies for all versions). I believe that historical setup versions will either ignore, or can handle depends: