On Mon, 30 Mar 2009, Manoj Srivastava wrote:
> On Mon, Mar 30 2009, Nils Rennebarth wrote:
> > Usually, unknown fields are iggnored by the debian packaging
> > system. To avoid conflicts of user defined fields with field that may
> > be used by debian in the future, we suggest to use field names
>
Nils Rennebarth writes:
> Usually, unknown fields are iggnored by the debian packaging system. To
> avoid conflicts of user defined fields with field that may be used by
> debian in the future, we suggest to use field names starting with X- (so
> you need to put X[BCS]-X-foo into the control file
On Mon, Mar 30 2009, Nils Rennebarth wrote:
>
> Please add something along the following lines to the section 5.7
> "User defined fields" to the debian policy manual:
>
> Usually, unknown fields are iggnored by the debian packaging
> system. To avoid conflicts of user defined fields with field tha
On Mon, 30 Mar 2009, Nils Rennebarth wrote:
> Package: debian-policy
> Version: 3.8.0.1
> Severity: wishlist
>
> Please add something along the following lines to the section 5.7
> "User defined fields" to the debian policy manual:
>
> Usually, unknown fields are iggnored by the debian packaging
Nils Rennebarth wrote:
Package: debian-policy
Version: 3.8.0.1
Severity: wishlist
Please add something along the following lines to the section 5.7
"User defined fields" to the debian policy manual:
Usually, unknown fields are iggnored by the debian packaging system. To
avoid conflicts of user
Package: debian-policy
Version: 3.8.0.1
Severity: wishlist
Please add something along the following lines to the section 5.7
"User defined fields" to the debian policy manual:
Usually, unknown fields are iggnored by the debian packaging system. To
avoid conflicts of user defined fields with field
6 matches
Mail list logo
