Jonathan Yu <[email protected]> writes:
> So this means they would be a good candidate to merge together, or for
> one to reference the other. For example if Section 5.6.7 would say:
> "Please see Section 5.6.1 for the naming conventions, binary package
> names follow the same restrictions as their source counterparts"
>
> It also means that programs working with those fields can reasonably
> expect that the syntax accepted by one field (the Source field) will not
> ever be out of sync from the other (the Package field). And it also
> means that one won't inadvertently update one while forgetting about the
> other.
>
> As this is a minor change I don't think that it needs seconds, once
> someone picks it up and pushes it to the master.
I've applied the following change:
diff --git a/policy.sgml b/policy.sgml
index 1eb6977..ffc721f 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -2605,11 +2605,12 @@ Package: libc6
</p>
<p>
- Package names must consist only of lower case letters
- (<tt>a-z</tt>), digits (<tt>0-9</tt>), plus (<tt>+</tt>)
- and minus (<tt>-</tt>) signs, and periods (<tt>.</tt>).
- They must be at least two characters long and must start
- with an alphanumeric character.
+ Package names (both source and binary,
+ see <ref id="f-Package">) must consist only of lower case
+ letters (<tt>a-z</tt>), digits (<tt>0-9</tt>), plus
+ (<tt>+</tt>) and minus (<tt>-</tt>) signs, and periods
+ (<tt>.</tt>). They must be at least two characters long and
+ must start with an alphanumeric character.
</p>
</sect1>
@@ -2708,11 +2709,9 @@ Package: libc6
</p>
<p>
- Package names must consist only of lower case letters
- (<tt>a-z</tt>), digits (<tt>0-9</tt>), plus (<tt>+</tt>)
- and minus (<tt>-</tt>) signs, and periods (<tt>.</tt>).
- They must be at least two characters long and must start
- with an alphanumeric character.
+ Binary package names must follow the same syntax and
+ restrictions as source package names. See <ref id="f-Source">
+ for the details.
</p>
</sect1>
--
Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
