On Thu, Aug 18, 2005 at 03:28:39AM -0500, Peter Samuelson wrote:
> You've got it. That was the point of contention. The real objection
Thanks for a lucid explanation, and my apologies for a late followup.
> If you think your package really is only useful on Debian-like systems,
> it may be o
[Jeroen Vermeulen]
> This is where we have our wires crossed: I'm still talking _only_
> about giving the Debian packaging a home in the same SCM repository.
> You'll remember that I said this is, from our point of view,
> primarily a Debian package and so the tarball is more of a byproduct.
> Whe
On Sat, Aug 13, 2005 at 11:16:36AM +0200, Henning Makholm wrote:
> If you have nothing against a clear separation between the upstream
> source and the Debian packaging, when why are you objecting when I say
> you should have one?
I am still not objecting to a clear separation per se, just to ha
Jeroen Vermeulen <[EMAIL PROTECTED]> writes:
> On Thu, Aug 11, 2005 at 11:07:44PM +0200, Goswin von Brederlow wrote:
>
>> You say "us" so I assume you are more then one person. Why not make
>> one of them (or all as a group) Debian maintainer of the package? Make
>> the package a debian native p
Scripsit Jeroen Vermeulen <[EMAIL PROTECTED]>
> On Thu, Aug 11, 2005 at 11:07:44PM +0200, Goswin von Brederlow wrote:
>> You do not have to be a Debian Developer to be a maintainer. As non DD
>> you only need a DD to sponsor your uploads.
> Thanks--that sounds like exactly what we need! The code
[Henning Makholm]
> Huh? Is your Debian packaging stuff written in Scheme?
SCM is probably meaning "Software Configuration Management" in this
context. 'dict scm' could have helped you find this.
> but if one's entire debian/ directory has to be created on top of
> existing files from upstream,
Scripsit Jeroen Vermeulen
> On Thu, Aug 11, 2005 at 06:28:07PM +0200, Henning Makholm wrote:
> > > For us, taking the Debian parts out might be just as awkward.
> > I really doubt that. Could you explain which problems you see with
> > having a clear separation?
> Don't put words into my mouth.
On Thu, Aug 11, 2005 at 11:07:44PM +0200, Goswin von Brederlow wrote:
> You say "us" so I assume you are more then one person. Why not make
> one of them (or all as a group) Debian maintainer of the package? Make
> the package a debian native package, which obviously includes a debian
> dir.
>
>
On Thu, Aug 11, 2005 at 06:28:07PM +0200, Henning Makholm wrote:
> > In this particular case though, Debian is the primary environment for
> > the program.
>
> That's not by itself a reason to include packaging-specific files in
> the upstream tarball.
Okay, fine. I'm just giving reasons I thi
Scripsit Jeroen Vermeulen <[EMAIL PROTECTED]>
> On Wed, Aug 10, 2005 at 01:00:59PM +0200, Henning Makholm wrote:
>
>> On the other hand integrating Debian's *packaging* infrastructure
>> (i.e., the debian/ subdirectory) in upstream source cannot be
>> recommended. It only creates trouble for develo
Scripsit Jeroen Vermeulen <[EMAIL PROTECTED]>
> On Wed, Aug 10, 2005 at 01:00:59PM +0200, Henning Makholm wrote:
>> On the other hand integrating Debian's *packaging* infrastructure
>> (i.e., the debian/ subdirectory) in upstream source cannot be
>> recommended. It only creates trouble for develop
On Wed, Aug 10, 2005 at 01:00:59PM +0200, Henning Makholm wrote:
> On the other hand integrating Debian's *packaging* infrastructure
> (i.e., the debian/ subdirectory) in upstream source cannot be
> recommended. It only creates trouble for developers when the policy
> and environment they are pack
Scripsit Jeroen Vermeulen <[EMAIL PROTECTED]>
> On Wed, Aug 10, 2005 at 04:30:22PM +1000, Anibal Monsalve Salazar wrote:
>> [Jeroen, you can be the owner of this ITP, if you wish so.]
> I'm not a Debian developer, so I'm probably not a useful owner.
You can maintain a package for Debian without
On Wed, Aug 10, 2005 at 04:30:22PM +1000, Anibal Monsalve Salazar wrote:
> Small, stable system add-on that continuously and automatically adapts
> available virtual memory space to your actual memory needs. Claims disk
> space
> for use as swap space when needed; frees it up for use by the
: GPLv2
Description : Dynamic swap space manager
Small, stable system add-on that continuously and automatically adapts
available virtual memory space to your actual memory needs. Claims disk space
for use as swap space when needed; frees it up for use by the filesystem when
not needed.
Hello,
I've written a dynamic swap space manager for GNU/Linux in the vein of
swapd and dynswapd--but in many ways better. We felt this was helpful in
a Debian-based system distribution for SMEs that we are releasing, where
we don't want to bother the sysadmin with unnecessary choi
16 matches
Mail list logo
