public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Goodyear <g2boojum@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] quixote currently unmaintained
Date: Tue, 1 Nov 2005 14:22:04 -0600	[thread overview]
Message-ID: <20051101202204.GC20491@bmb24.uth.tmc.edu> (raw)
In-Reply-To: <20051031214102.GA22683@bmb24.uth.tmc.edu>

[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]

Okay, it seems that I should have provided many more details.

Quixote is "A simple but powerful Web development framework for Python
programmers".  It's very low-level, but at the same time it's
exceedingly sane.  When I added quixote to portage it was just going
through its 1.0 release.  I'm still not entirely comfortable handling
webapp-based ebuilds, but quixote itself is not too difficult to
maintain by itself.  In practice, though, people using quixote are
likely to want to any of the following support packages that have sprung
up over the last year or two: durus (object database), dulcinea
(quixote/dulcinea helper modules), scgi (alternative to fast-cgi),
and Sancho (Python unit-testing framework).  Many of the packages have
ebuilds in bugs, but to date nobody has been willing to maintain them.
I'm not that interested in web applications myself, so I'm unwilling to
invest the time necessary to make sure that Gentoo has a functional
quixote + helpers framework.  *Shrug*  The result is that Gentoo's
support for quixote is horribly inadequate.  

My view is that if a package is in the tree, then there's an implicit
understanding that we're maintaining it.  If we're not, then I really
think it should go away.  (Note, by the way, that this argument is
completely unrelated to whether or not we should have
upstream-unmaintained packages in the tree.  As long as a Gentoo dev is
willing to look after those packages when necessary, then I see no
reason we shouldn't have those packages.)

-g2boojum-
-- 
Grant Goodyear	
Gentoo Developer
g2boojum@gentoo.org
http://www.gentoo.org/~g2boojum
GPG Fingerprint: D706 9802 1663 DEF5 81B0  9573 A6DC 7152 E0F6 5B76

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2005-11-01 20:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 21:41 [gentoo-dev] quixote currently unmaintained Grant Goodyear
2005-10-31 21:44 ` Petteri Räty
2005-11-01 17:04   ` Carsten Lohrke
2005-11-01 17:11     ` Re[2]: " Jakub Moc
2005-11-01 17:40       ` Carsten Lohrke
2005-11-01 17:55         ` Re[2]: " Jakub Moc
2005-11-01 17:43     ` Jon Portnoy
2005-11-01 18:40       ` Carsten Lohrke
2005-11-01 18:49       ` Ciaran McCreesh
2005-11-01 19:39         ` Diego 'Flameeyes' Pettenò
2005-11-01 17:25   ` Diego 'Flameeyes' Pettenò
2005-11-01 20:22 ` Grant Goodyear [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051101202204.GC20491@bmb24.uth.tmc.edu \
    --to=g2boojum@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox