On 22/09/2023 00.22, Ulrich Mueller wrote:
>> On Thu, 21 Sep 2023, Arthur Zamarin wrote:
>
>> = "Formal" format =
>
>> Each entry is composed of 2 parts: "#"-prefixed explanation block and
>> list of "${CATEGORY}/${PN}" packages. Entries are separated when a new
>> explanation block s
On 22/09/2023 12.21, Ulrich Mueller wrote:
>> On Fri, 22 Sep 2023, Oskari Pirhonen wrote:
>
>>> Each entry is composed of 2 parts: "#"-prefixed explanation block and
>>> list of "${CATEGORY}/${PN}" packages. Entries are separated when a new
>>> explanation block starts (meaning first "#"-prefi
> On Fri, 22 Sep 2023, Oskari Pirhonen wrote:
>> Each entry is composed of 2 parts: "#"-prefixed explanation block and
>> list of "${CATEGORY}/${PN}" packages. Entries are separated when a new
>> explanation block starts (meaning first "#"-prefixed line after packages
>> list). You may add new
On Thu, Sep 21, 2023 at 22:40:05 +0300, Arthur Zamarin wrote:
> = "Formal" format =
>
> Each entry is composed of 2 parts: "#"-prefixed explanation block and
> list of "${CATEGORY}/${PN}" packages. Entries are separated when a new
> explanation block starts (meaning first "#"-prefixed line
On Thu, Sep 21, 2023 at 23:22:27 +0200, Ulrich Mueller wrote:
> > On Thu, 21 Sep 2023, Arthur Zamarin wrote:
>
> > = "Formal" format =
>
> > Each entry is composed of 2 parts: "#"-prefixed explanation block and
> > list of "${CATEGORY}/${PN}" packages. Entries are separated when a new
Tim Harder writes:
> On 2023-09-21 Thu 15:22, Ulrich Mueller wrote:
>>> On Thu, 21 Sep 2023, Arthur Zamarin wrote:
>>> Should it be a GLEP, I don't think so? But I'm unsure about it. We do
>>> need to document it (for example header of that exact file).
>>
>>It shouldn't be too difficult to
On 2023-09-21 Thu 15:22, Ulrich Mueller wrote:
On Thu, 21 Sep 2023, Arthur Zamarin wrote:
Should it be a GLEP, I don't think so? But I'm unsure about it. We do
need to document it (for example header of that exact file).
It shouldn't be too difficult to wrap this up as a GLEP.
To me standard
> On Thu, 21 Sep 2023, Arthur Zamarin wrote:
> = "Formal" format =
> Each entry is composed of 2 parts: "#"-prefixed explanation block and
> list of "${CATEGORY}/${PN}" packages. Entries are separated when a new
> explanation block starts (meaning first "#"-prefixed line after package
Hi all
I want to suggest a standard format for profiles/package.mask, for
multiple reasons:
1. Easier to write simple to understand mask or last-rites entries. When
all entries are in similar format, the reader knows where to expect
important information and such. Also easier for writer to convey
