On Wed, 7 Jun 2023 at 11:46, Luca Boccassi wrote:
>
> On Wed, 7 Jun 2023 at 11:29, Simon McVittie wrote:
> >
> > On Tue, 06 Jun 2023 at 20:40:52 -0700, Russ Allbery wrote:
> > > Luca Boccassi writes:
> > > > +Packages might need additional files or directories to implement their
> > > > +functio
On Tue, Jun 06, 2023 at 11:34:17PM +0100, Luca Boccassi wrote:
> On Wed, 7 Jun 2023 00:01:42 +0200 Bill Allombert
> > This is beside the point. Your problematic statement was
> > "The whole project is moving toward git and Salsa ".
> > This is not conducive of productive interaction.
>
> It was n
On Wed, Jun 07, 2023 at 08:19:08AM -0700, Russ Allbery wrote:
> I would like to add more documentation like this around systemd-related
> things to Policy because systemd is complicated and has a lot of options,
> so people who aren't deeply familiar with it will easily miss best
> practices in its
On Wed, Jun 07, 2023 at 08:19:08AM -0700, Russ Allbery wrote:
> > In general, policy proscription are only useful when the description of
> > a better mechanism is provided. But there is no place for that in this
> > section.
>
> I'm not sure I understand this statement, since describing a better
Bill Allombert writes:
> On Tue, Jun 06, 2023 at 07:56:14PM -0700, Russ Allbery wrote:
>> I prefer that too, but in this case, it feels like must is appropriate
>> for at least systemd configuration files. And also, just intuitively,
>> I feel like must is correct when people are using diversion
On Wed, 7 Jun 2023 12:23:15 +0200 Bill Allombert
wrote:
> On Tue, Jun 06, 2023 at 07:56:14PM -0700, Russ Allbery wrote:
> > Sean Whitton writes:
> >
> > > I think what's a bit peculiar here is using "must" for a case
where
> > > there might be package-specific exceptions. In other cases,
Policy
On Wed, 7 Jun 2023 at 11:29, Simon McVittie wrote:
>
> On Tue, 06 Jun 2023 at 20:40:52 -0700, Russ Allbery wrote:
> > Luca Boccassi writes:
> > > +Packages might need additional files or directories to implement their
> > > +functionality. Directories that are located under ``/var/`` or
> > > +``
On Tue, Jun 06, 2023 at 07:56:14PM -0700, Russ Allbery wrote:
> Sean Whitton writes:
>
> > I think what's a bit peculiar here is using "must" for a case where
> > there might be package-specific exceptions. In other cases, Policy uses
> > "should" for these cases. Typically "must" rules are sim
On Wed, 7 Jun 2023 at 04:40, Russ Allbery wrote:
>
> Luca Boccassi writes:
>
> > diff --git a/policy/ch-files.rst b/policy/ch-files.rst
> > index b34c183..30ce013 100644
> > --- a/policy/ch-files.rst
> > +++ b/policy/ch-files.rst
> > @@ -722,6 +722,43 @@ The name of the files and directories inst
On Tue, 06 Jun 2023 at 20:40:52 -0700, Russ Allbery wrote:
> Luca Boccassi writes:
> > +Packages might need additional files or directories to implement their
> > +functionality. Directories that are located under ``/var/`` or
> > +``/etc/``, and files that are located under ``/var/``, must not be
On Tue, Jun 06, 2023 at 07:52:35PM -0700, Russ Allbery wrote:
> Bill Allombert writes:
> > On Sun, Jun 04, 2023 at 12:25:54PM +0100, Luca Boccassi wrote:
>
> >> If you prefer, I can reword the general rule to be stricter, ie:
> >> "packages must not use diversions where native mechanisms are
> >>
11 matches
Mail list logo
