On 05-Mar-2009, Charles Plessy wrote:
> at the same time, your patch would make it mandatory to write a
> get-orig-source target when uscan(1) can not do the job. […] Can you
> soften your wording to the current "optional" status ?
Agreed. I also should have used the standard document markup for
v
On Thu, Mar 05, 2009 at 11:46:48AM +0100, Wouter Verhelst
wrote:
> The game data defines what game you play; the engine
> defines _how_ you play it. Personally, I couldn't care
> less how exactly a game is run on my system, as long as it
> is a game I like. IOW, the data is what the user will
> cho
On Thu, Mar 05, 2009 at 11:03:57AM +0100, Giacomo A. Catenazzi wrote:
> Jon Dowland wrote:
>> A brief explanation as to their meaning. Doom games are
>> divided into engine and world-resource components. The
>> former is captured by 'doom-engine'.
>
> I don't understand why we need a 'doom-engine'
On Thu, Mar 05, 2009 at 01:27:31PM +0100, Giacomo A. Catenazzi wrote:
> a 'boom-wad' should depend on the virtual engine: 'doom-engine',
> a 'doom-wad' should depend on the virtual engine: 'doom-engine'.
> but not all doom-engines support boom data. This was my confusion:
> two virtual package on d
Le Thu, Mar 05, 2009 at 08:39:50PM +1100, Ben Finney a écrit :
>
> I've proposed a patch to policy (in bug#466550) to bring policy in
> line with this practice.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466550#42
- This target is optional, but providing it if
Wouter Verhelst wrote:
On Thu, Mar 05, 2009 at 11:03:57AM +0100, Giacomo A. Catenazzi wrote:
Jon Dowland wrote:
A brief explanation as to their meaning. Doom games are
divided into engine and world-resource components. The
former is captured by 'doom-engine'.
I don't understand why we need a '
On Thu, Mar 05, 2009 at 11:03:57AM +0100, Giacomo A. Catenazzi wrote:
> Jon Dowland wrote:
>> A brief explanation as to their meaning. Doom games are
>> divided into engine and world-resource components. The
>> former is captured by 'doom-engine'.
>
> I don't understand why we need a 'doom-engine'
Jon Dowland wrote:
A brief explanation as to their meaning. Doom games are
divided into engine and world-resource components. The
former is captured by 'doom-engine'.
I don't understand why we need a 'doom-engine' virtual package.
[i.e.: avoid circular dependencies].
IMHO, a user will select a
Processing commands for cont...@bugs.debian.org:
> package debian-policy
Ignoring bugs not assigned to: debian-policy
> tags 466550 + patch
Bug#466550: Clarify or remove the get-orig-source target specification
There were no tags set.
Tags added: patch
> thanks
Stopping processing here.
Please
package debian-policy
tags 466550 + patch
thanks
On 19-Feb-2008, Andres Mejia wrote:
> When considering the phrase in policy "...does any necessary
> rearrangement to turn it into the original source tar file
> format...", it makes more sense when it refers to the original
> source tar file of the
On 21-Feb-2008, Manoj Srivastava wrote:
> the question now is whether this directive actually makes sense as
> policy at this point. It obviously does not reflect common
> practice, since the common practice is not to implement this
> target.
Practice is, I think, changing recently in respons
11 matches
Mail list logo
