Manoj Srivastava <[EMAIL PROTECTED]> writes:
> This brings up another issue about rule datasets: namespaces and
> name collisions. How should rule entities be named, in order to
> minimize conflict?
> We can try using clever abbreviations of the rule title, but
> that seems a
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> On Mon, 3 Dec 2007 10:21:10 -0500, Eric Cooper <[EMAIL PROTECTED]> said:
>> I had the same initial reaction, but when I re-read Manoj's
>> introduction, I think he suggests that this docbook format should be
>> the *output* of an XSLT tool; the vario
Stefano Zacchiroli <[EMAIL PROTECTED]> writes:
> Unfortunately I'm writing this email offline so I'm unable to check
> whether docbook has any more appropriate element for this or where else
> can be but a element, but something better then this should
> be looked for.
One thing that's definitel
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> With this in mind, I have created an initial draft format of the
> Debian technical policy set, and am including it in this mail.
>
> Comments appreciated.
[...]
>
> Policy Rule Example
>
>
>
Colin Watson <[EMAIL PROTECTED]> writes:
> I propose that policy should standardise that we move to using UTF-8 as
> the source encoding for all manual pages since it clearly makes sense to
> do so. This will still need to be specified by each manual page (by
> means of the directory in which it i
Mario Iseli <[EMAIL PROTECTED]> writes:
> Package: debian-policy
> Severity: normal
> Tags: patch
>
> I think the Homepage field for debian/control is now official - at least
> it isn't documented in the policy right now. So here - a little patch
> which would fix that.
Here is a somewhat revised
Ian Jackson <[EMAIL PROTECTED]> writes:
> Raphael Hertzog writes:
>> On Tue, 30 Oct 2007, Ian Jackson wrote:
>>> After all the surprise is that the package became installed.
>>> Redefining the postinst's semantics so that the package doesn't count
>>> as installed in this case is the wrong answer
I generally agree with Ian that several of the changes proposed here don't
seem clearly better to me. A few others have already been made, namely:
> Michael Tautschnig writes ("Bug#422552: Minor typos and wording suggestions"):
>> - Page 8, 2.5 Priorities, Paragraph on "required": s/Removing an
Bernd Zeimetz <[EMAIL PROTECTED]> writes:
> also contrib and non-free are listed in the sections, imho they should
> be removed there, that's what we have categories for.
Agreed. Those look misplaced. Does anyone disagree? For reference, the
text we're talking about is:
The category and
Robert Millan <[EMAIL PROTECTED]> writes:
> On Sat, Jun 30, 2007 at 12:17:00AM +0200, Santiago Vila wrote:
>>
>> Instead, I think we should amend policy in this way:
>>
>> Packages under a fixed, definite version of the GPL should refer to
>> the versioned GPL file in /usr/share/common-licens
Josh Triplett <[EMAIL PROTECTED]> writes:
> Package: debian-policy
> Version: 3.7.3.0
> Severity: minor
>
> Policy 7.2:
>>(The other three dependency fields, `Recommends', `Suggests' and
>> `Enhances', are only used by the various front-ends to `dpkg' such
>> as `dselect'.)
>
> Since apt uses Reco
Magnus Holmgren <[EMAIL PROTECTED]> writes:
> Source: debian-policy
> AFAIU, the base subsection was obsoleted with Etch (apparently, its
> removal was discussed already in 1997), and (almost) all packages moved
> to ordinary subsections, like other packages. However, it is still
> listed in sect
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.11
> tags 209008 patch
Bug#209008: debian-policy: [PROPOSAL] common interface for parallel building in
DEB_BUILD_OPTIONS
There were no tags set.
Tags added: patch
>
End of message, stop
Okay, here's a revised proposal to address both Bug#209008 (parallel) and
Bug#430649 (DEB_BUILD_OPTIONS parsing). This proposal does the following:
* Standardizes on space as the separator for DEB_BUILD_OPTIONS. This
only affects what people can pass into debian/rules, not any existing
pa
Loïc Minier <[EMAIL PROTECTED]> writes:
> - separating with commas prevents passing options with commas; a sample
>use case which might be useful in the near future could be passing
>CFLAGS/LDFLAGS via DEB_BUILD_OPTIONS, and some of these flags require
>commas to reach the linker/asse
On Sun, 30 Dec 2007, Russ Allbery wrote:
> Raphael Hertzog <[EMAIL PROTECTED]> writes:
> > On Mon, 24 Dec 2007, Manoj Srivastava wrote:
>
> >> I have since used that framework, and I am proposing expanding
> >> the user tags and using the user debian-policy@lists.debian.org as the
> >> d
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> On Mon, 24 Dec 2007, Manoj Srivastava wrote:
>> I have since used that framework, and I am proposing expanding
>> the user tags and using the user debian-policy@lists.debian.org as the
>> default user. I have expanded on the scheme used by
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> This is going to be a long email. I am contemplating the
> holiday festivities, and am getting into the zen mode for making
> traditional egg nog. Where I live, traditional egg nog means
> contemplating very old Kentucky straight bourbon
Colin Watson <[EMAIL PROTECTED]> writes:
> This has the unfortunate property of excluding Gnulib, which is a
> library of code explicitly designed by the GNU build system folks to
> live alongside the Autotools and be copied into packages to provide
> replacements for missing functions. Perhaps so
hi,
> I would like to add a menu section for my program "gpr" (Description:
> GUI for lpr: print files and configure printer-specific options) but I
> am a bit at loss, since in /usr/share/doc/debian-policy/menu-policy.txt.gz
> I cannot really find a section that would fit. Any suggestion?
You pr
We congratulate on coming holidays
Get ready for Christmas holidays with a new you
http://dobongworld.com
And when the sun went down,
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
All the best!
Get ready for Christmas holidays with a new you
http://dobongworld.com
To the echoing sound of a coppery gong,
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
All the best!
Get ready for Christmas holidays with a new you
http://dobongworld.com
And all the Sailors and Admirals cried,
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
All blessings!
Get ready for Christmas holidays with a new you
http://beaverbonghits.com
And they passed the night in a crockery-jar,
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
All Good!
Get ready for Christmas holidays with a new you
http://dobongworld.com
But we don't care a button! we don't care a fig!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Good afternoon!
Get ready for Christmas holidays with a new you
http://beaverbonghits.com
They sailed away in a Sieve, they did,
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
hi
I would like to add a menu section for my program "gpr" (Description:
GUI for lpr: print files and configure printer-specific options) but I
am a bit at loss, since in /usr/share/doc/debian-policy/menu-policy.txt.gz
I cannot really find a section that would fit. Any suggestion?
a.
signature
Good evening!
Get ready for Christmas holidays with a new you
http://dobongworld.com
Which they ate with a runcible spoon;
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
28 matches
Mail list logo
