Bug#448756: ITP: dmucs -- distributed compilation system for use with distcc
Package: wnpp Severity: wishlist Owner: Sam Clegg <[EMAIL PROTECTED]> * Package name: dmucs Version : 0.6.1 Upstream Author : Victor Norman <[EMAIL PROTECTED]> * URL : http://dmucs.sourceforge.net/ * License : GPL Programming Lang: C Description : distributed compilation system for use with distcc DMUCS is a system that allows a group of users to share a compilation farm. Each compilation request from each user will be sent to the fastest available machine, every time. The system has the following features: * Supports multiple users compiling simultaneously, and scales well to handle the new loads. * Supports multiple operating systems in the compilation farm. * Uses all processors of a multi-processor compilation host. * Makes best use of compilation hosts with widely differing CPU speeds. * Guarantees that a compilation host will not be overloaded by compilations. * Takes into account the load on a host caused by non-compilation tasks. * Supports the dynamic addition and removal of hosts to the compilation farm. * Works with distcc, which need not be altered in any way. You can get my initial package from here: http://superduper.net/downloads/debian/dmucs_0.6.1-1_i386.deb -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#445866: ITP: perforce -- closed source revision control system
On Tue, 2007-10-09 at 05:41 +0300, Faidon Liambotis wrote: > Daniel Jacobowitz wrote: > > On Mon, Oct 08, 2007 at 03:41:21PM -0400, Roberto C. S?nchez wrote: > >> Given the great abundance of revision control systems already packaged > >> for Debian, what is the point of adding another? Especially when it is > >> non-free. > > > > How about "people use it"? There's plenty of installations of > > perforce; I think making it easier to use Debian with them is > > within the mandate for non-free. > I'd say upload only the client to non-free. > > We should provide users a way to use their existent preforce servers but > we should not encourage new installations of perforce. > > Sounds like a compromise to me :) Indeed, my primary aim was to make it easy for anyone wanting to run debian in an org that uses perforce (i.e. people like myself). I agree the server package is of less use in this respect, its simply there to make it easy for people to choose debian on the server side as well. Pending the legal conclusions I'll upload just the client package initially. signature.asc Description: This is a digitally signed message part
Re: Bug#445866: ITP: perforce -- closed source revision control system
On Mon, 2007-10-08 at 14:42 -0700, Tyler MacDonald wrote: > Florian Weimer <[EMAIL PROTECTED]> wrote: > > Seems to me that this depends on Perforce. D'oh. > > > > (I don't know anything about Perforce. Perhaps it's really dangerous > > software. But perhaps it's just non-free.) > > Perforce is an absolutely *excellent* VCS with the unfortunate > distinction of being proprietary. SubVersion can do most (but not all) of > what it does, albeit 10 times slower. Still, I've migrated all of my stuff > over to subversion, because, well, subversion is free. Perforce is free (as > in "free beer") for open source developers, if you want more than 2 users on > one VCS server, you have to sign a contract, get a license, give the > perforce people full access to your repo, sign a new contract whenever you > server's IP address changes, and renew each year Slightly off topic, but you don't need to give the perforce people access to you repo (unless you really want them to come in a fix something) and you don't need to renew each year (unless you want support from them). signature.asc Description: This is a digitally signed message part
Bug#445866: ITP: perforce -- closed source revision control system
Package: wnpp Severity: wishlist Owner: Sam Clegg <[EMAIL PROTECTED]> * Package name: perforce Version : 2007.2-2 Upstream Author : Perforce Inc. <[EMAIL PROTECTED]> * URL : http://www.perforce.com/ * License : proprietary Programming Lang: binary only (with bindings in Perl, Python, etc.) Description : closed source revision control system closed source, centralised source control system akin to CVS and subversion. You'll need a license to run a server with more than two users. Free licenses are granted to open source projects. I'm in talks with perforce to get explicit permission to distribute in non-free. Current license discussions are here: http://lists.debian.org/debian-legal/2007/09/msg00184.html My packages are here: http://superduper.net/downloads/debian/ I've created two packages: 'perforce' for the client and 'perforce-server' for the server. The 'perforce-server' package is a 'fat' package that contains many server binaries (since the users license if normally limited to a given version). The server package contains debian-friendly init scripts, etc. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380190: ITP: sqliteodbc -- ODBC driver for SQLite embedded database
Package: wnpp Severity: wishlist Owner: Sam Clegg <[EMAIL PROTECTED]> * Package name: sqliteodbc Version : 0.69 Upstream Author : Christian Werner <[EMAIL PROTECTED]> * URL : http://www.ch-werner.de/sqliteodbc/ * License : BSD-style Programming Lang: C Description : ODBC driver for SQLite embedded database This package allows you to connect to an SQLite database using ODBC, the Open Database Connectivity abstraction layer which is understood by a variety of database tools that may not be able to talk to SQLite directly. Experimental pacakge here: http://superduper.net/downloads/debian/libsqliteodbc_0.69-1_i386.deb Sources here: http://superduper.net/downloads/debian/sources/ (Include the long description here.) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#310044: ITP: proguard -- java class file shrinker, optimizer, and obfuscator
Package: wnpp Severity: wishlist Owner: Sam Clegg <[EMAIL PROTECTED]> * Package name: proguard Version : 3.2 Upstream Author : Eric Lafortune <[EMAIL PROTECTED] * URL : http://proguard.sourceforge.net/ * License : GPL Description : java class file shrinker, optimizer, and obfuscator ProGuard is a free Java class file shrinker, optimizer, and obfuscator. It can detect and remove unused classes, fields, methods, and attributes. It can then optimize bytecode and remove unused instructions. Finally, it can rename the remaining classes, fields, and methods using short meaningless names. The resulting jars are smaller and harder to reverse-engineer. This package builds just with jikes-classpath and runs with kaffe which are both in main. My provisional packages are available here: http://people.debian.org/~samo/experimental/ There is an archived ITP for proguard from over a year ago and I have checked with the original filer that he is no longer interested in this package. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.11 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#304948: ITP: boo -- a python-like language and compiler for the CLI
Package: wnpp Severity: wishlist Owner: Sam Clegg <[EMAIL PROTECTED]> * Package name: boo Version : 0.5 Upstream Author : Rodrigo B. de Oliveira <[EMAIL PROTECTED]> * URL : http://boo.codehaus.org/ * License : Custom. DFSG Compatible. Description : a python-like language and compiler for the CLI Boo is considered ready for general usage and runs fine on mono. In fact mono its the primary target platform. The licence is custom but looks DFSG compatible. My initial boo package is here: http://people.debian.org/~samo/experimental/ Long Description: Boo is an object oriented statically typed programming language for the Common Language Infrastructure (CLI) with a Python inspired syntax and a special focus on language and compiler extensibility. . This package includes the Boo libraries as well as a compiler, interpreter and interactive shell. The boo compiler and the programs it produces are 100% CIL and can be run on any compliant CLI virtual machine. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.11-1-686-smp Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Future releases of Debian
On Tue, Jul 29, 2003 at 08:55:15AM +0200, Marc Haber wrote: > Actually, when I was stuck in the DAM queue for half a year without > getting a single word of feedback, I wouldn't have dreamt to ask for > an account for two reasons: How long would it take for you to ask questions? 1 year? 2 years? > (1) There were rumours that asking questions while on the DAM queue > can arbitrarily extend your time on that queue. I agree with your reasons though, which is why I havn't been pestering the DAM about my account, but one day I think I'm going to have to at least ask whats going on :( -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ pgpQbYKtOSBFz.pgp Description: PGP signature
Re: maildirmake
On Tue, Jun 24, 2003 at 09:45:30AM +0200, Ralf Hildebrandt wrote: > * Andreas Metzler <[EMAIL PROTECTED]>: > > > You could start by telling us what maildirmake is supposed to do. Why > > do we need it? Any program I know of which can handle Maildir is not > > only capable of storing messages in Maildir folders but also of > > generating them. This includes e.g. the exim(4) MTA, MDAs like > > procmail or maildrop, and the MUA mutt. > > Same for Postfix. > Who needs maildirmake? IIRC courier-imap expects ~/Maildir to exist before you can check your mail (but maildirmake ships with courier-base). -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ pgpjWcShwCS3a.pgp Description: PGP signature
Re: pam_console for debian
On Thu, Jul 25, 2002 at 10:23:09AM -0700, David Caldwell wrote: > Sounds like what you really want is a way to take exclusive access to the > camera device somehow. Can you exclusively open the device and prevent > others from opening it too? I suppose even that would have a timing > splinter: Someone could take exclusive control before you got a chance... I would like to see someting like this for hotpluggable storage as well. If I want to keep private data (private keys etc) on a USB keyring I would like to be sure that nobody else can mount it before me. Perhaps the hotplug system could implement some kind of method for a user to say "any device plugged in the next 1 minute is mine". Clearly this is vulnerable to DoS by others but this is far better than others being able to mount your disks/read your photos. sam -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP :: D91EE369 $superduper: .signature,v 1.5 2002/05/17 10:23:59 samc Exp $ pgp9E4KeulXHJ.pgp Description: PGP signature
