Carl Worth writes:
> That is, surely there must be a way for you to keep the debian
> directory in the single repository along with the implementation and
> still build a non-native package from it. That would seem to me the
> ideal way to go.
http://www.eyrie.org/~eagle/notes/debian/git.html
a
Excerpts from Jens Peter Secher's message of Fri Sep 04 11:12:47 -0700 2009:
> FWIW, I wrote this answer (but did not send it):
Funny, because I received it. :-)
> There is no point pretending there is an upstream when there clearly
> isn't. Pretending there is an upstream just forces me put eve
2009/9/4 Gunnar Wolf :
> Wouter Verhelst dijo [Thu, Sep 03, 2009 at 12:47:44PM +0200]:
>> > > * Upstream has abandoned the program, so the package is now Debian
>> > > native.
>> >
>> > Switching upstreams does not make a package native.
>>
>> How so? There is no reason why a package where th
Wouter Verhelst dijo [Fri, Sep 04, 2009 at 09:01:47AM +0200]:
> On Thu, Sep 03, 2009 at 06:29:31PM -0500, Gunnar Wolf wrote:
> > Why should it be Debian-native?
>
> I never said it *should* be. I said it *could* be, and that whether or
> not it is should be the maintainer's prerogative.
Bad choic
On Thu, Sep 03, 2009 at 06:29:31PM -0500, Gunnar Wolf wrote:
> Why should it be Debian-native?
I never said it *should* be. I said it *could* be, and that whether or
not it is should be the maintainer's prerogative.
--
The biometric identification system at the gates of the CIA headquarters
work
Wouter Verhelst dijo [Thu, Sep 03, 2009 at 12:47:44PM +0200]:
> > > * Upstream has abandoned the program, so the package is now Debian
> > > native.
> >
> > Switching upstreams does not make a package native.
>
> How so? There is no reason why a package where the upstream and the
> Debian D
Wouter Verhelst wrote:
> I know it is fancy and modern to think that Debian native packages
> should only be used for things that are specific to the Debian
> infrastructure, but there is nothing in policy that requires that, and
> indeed several packages (including, e.g., offlineimap) are distribu
On Wed, Sep 02, 2009 at 07:09:01PM +, Sune Vuorela wrote:
> >>From the changelog:
> >
> > * Upstream has abandoned the program, so the package is now Debian
> > native.
>
> Switching upstreams does not make a package native.
How so? There is no reason why a package where the upstream an
On 2009-09-02, Jens Peter Secher wrote:
> 2009/9/2 Torsten Werner :
>>
>> why is it a native package? Why do we need this package in Debian that got
>> removed recently from unstable? I would expect an explanation either in bug
>> #541265 or in the changelog.
>
>>From the changelog:
>
> * Upstre
2009/9/2 Torsten Werner :
>
> why is it a native package? Why do we need this package in Debian that got
> removed recently from unstable? I would expect an explanation either in bug
> #541265 or in the changelog.
>From the changelog:
* Upstream has abandoned the program, so the package is now
10 matches
Mail list logo
