> "Sean" == Sean Whitton writes:
Sean> In general, I agree with Santiago. I find Policy's current
Sean> scope and working process effective, and not especially
Sean> ambiguous. I think everyone should read it during the NM
Sean> process, if not sooner.
Sean> Russ has
Hello,
On Mon 11 Sep 2023 at 01:04pm +02, Santiago Vila wrote:
> I wrote:
>> I believe that by choosing the wording appropriately, we can still keep this
>> desired property of Policy while still not mandating any given
>> implementation.
>
> Sorry, that was terribly worded. I meant that we can
Hello Russ,
In my view the main purpose of policy is to allow interoperability by defining
interfaces between packages.
We used to have a separate Packaging Manual, but it has been merged with
Policy a long time ago. The intent was to reduce duplication which lead to
outdated information.
Russ Allbery:
Niels Thykier writes:
Russ Allbery:
Ooo, this is a great framing of the problem. I have a lot of thoughts
about this. Unfortunately, I'm not sure if they're actionable thoughts
since my grand vision requires someone to sit down and do some serious
Policy restructuring and
Niels Thykier writes:
> Russ Allbery:
>> Ooo, this is a great framing of the problem. I have a lot of thoughts
>> about this. Unfortunately, I'm not sure if they're actionable thoughts
>> since my grand vision requires someone to sit down and do some serious
>> Policy restructuring and produce
Russ Allbery:
Niels Thykier writes:
I had a look at the introduction section of Policy to check who the
target audience is. I cannot find an explicit mention of the target
audience. I suspect there is a conflict here on the content because we
have different audiences in mind for the Policy
Niels Thykier writes:
> I had a look at the introduction section of Policy to check who the
> target audience is. I cannot find an explicit mention of the target
> audience. I suspect there is a conflict here on the content because we
> have different audiences in mind for the Policy and the
Russ Allbery:
Bill Allombert writes:
[...] Quite a lot of Policy is of the general format "here's a bunch of
complex things you need to do, wait, never mind, just use debhelper, go
see its documentation for the configuration files you should use instead"
and some of the rest of Policy is
Bill Allombert writes:
> But we do: we support debhelper 13.11.4 and debhelper 13.11.6. Even if
> we support a single implementation, we still need to know what is
> expected of it.
Policy already requires a single implementation of quite a lot of tools,
does not specify a version, and does
> "Bill" == Bill Allombert writes:
Bill> But we do: we support debhelper 13.11.4 and debhelper 13.11.6.
Bill> Even if we support a single implementation, we still need to
Bill> know what is expected of it.
At that level, I think the answer is roughly that if you call
On Mon, Sep 11, 2023 at 09:21:56AM -0600, Sam Hartman wrote:
> > "Santiago" == Santiago Vila writes:
>
> Santiago> El 10/9/23 a las 4:09, Russ Allbery escribió:
> >> I therefore would like to propose a first: I think Policy should
> >> simply say that any package that provides a
> "Santiago" == Santiago Vila writes:
Santiago> El 10/9/23 a las 4:09, Russ Allbery escribió:
>> I therefore would like to propose a first: I think Policy should
>> simply say that any package that provides a system service should
>> use debhelper and rely on
On Mon, Sep 11, 2023 at 12:47:15PM +0200, Santiago Vila wrote:
> El 10/9/23 a las 4:09, Russ Allbery escribió:
> > I therefore would like to propose a first: I think Policy should simply
> > say that any package that provides a system service should use debhelper
> > and rely on dh_installsystemd
I wrote:
I believe that by choosing the wording appropriately, we can still keep this
desired property of Policy while still not mandating any given implementation.
Sorry, that was terribly worded. I meant that we can avoid the hassle of
documenting everything dh_installsystemd does and at the
El 10/9/23 a las 4:09, Russ Allbery escribió:
I therefore would like to propose a first: I think Policy should simply
say that any package that provides a system service should use debhelper
and rely on dh_installsystemd to put the appropriate commands in its
maintainer scripts. (We can then
> "Russ" == Russ Allbery writes:
Russ> I therefore would like to propose a first: I think Policy
Russ> should simply say that any package that provides a system
Russ> service should use debhelper and rely on dh_installsystemd to
Russ> put the appropriate commands in its
Please remove the following email address: e.little...@gmail.com
On Sat, Sep 9, 2023 at 10:12 PM Russ Allbery wrote:
> Package: debian-policy
> Version: 4.6.2.0
> Severity: important
> X-Debbugs-Cc: r...@debian.org
>
> As part of reviewing #1039102, I took a detailed look at Policy 9.3
> on
Package: debian-policy
Version: 4.6.2.0
Severity: important
X-Debbugs-Cc: r...@debian.org
As part of reviewing #1039102, I took a detailed look at Policy 9.3
on system services and realized that it is largely obsolete and is
not followed by most Debian packages that provide system services.
18 matches
Mail list logo
