From: Peter Fein <pfein@pobox.com>
To: Brian Jackson <brian@mdrx.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Ebuilds not getting in :(
Date: Wed, 23 Apr 2003 10:27:00 -0500 [thread overview]
Message-ID: <20030423102700.5c720818.pfein@pobox.com> (raw)
In-Reply-To: <200304222156.16419.brian@mdrx.com>
On Tue, 22 Apr 2003 21:56:16 -0500
Brian Jackson <brian@mdrx.com> wrote:
> I know talking to myself this much in one day is bad, but I setup an rsync
> server. It is at:
> rsync://www.mdrx.com/portage-local
>
> you can run the following to check it out:
> rsync -rz rsync://www.mdrx.com/portage-local .
Actually, more formal support for multiple sync sources would be *highly*
cool & would really make portage a "meta-distribution". I could also see this
being useful for officially supported builds, as this readily solves the "I
never want to even sync anything X11" problem.
On a (barely) related extensibility note, I've found it really hard to work on
even short patches to portage/emerge. portage.py is almost 4600 lines, emerge
is almost 1900. My point being that's a pretty good size for a single code unit
in any language, but enormous for python. Try
find /usr/lib/python2.2/ -iname "*.py" |xargs wc -l |sort -n -r
and keep in mind that the standard modules have a lot more documentation. And
to cut off the inevitable criticism of this metric, these modules do import each
other & use C libs. That's my point. The lack of modularity & the presence of
top-level code makes reuse really tough- I'd love to work on a GTK'd or web'd
emerge or 30 other scripts, but everything's so intertwined that it's not
feasible to reuse code.
More user whining, I know. I don't quite know what I'm suggesting as a
solution, short of offering to help.
--Pete
--
Peter Fein
pfein@pobox.com
773-575-0694
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-04-23 15:27 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 7:38 [gentoo-dev] Ebuilds not getting in :( Klavs Klavsen
2003-04-22 12:59 ` Frantz Dhin
2003-04-22 13:09 ` Ragnar Hojland Espinosa
2003-04-22 13:17 ` Peter Ruskin
2003-04-22 13:24 ` FRLinux
2003-04-22 13:30 ` Klavs Klavsen
2003-04-22 13:50 ` Ragnar Hojland Espinosa
2003-04-22 14:05 ` Jon Portnoy
2003-04-22 16:18 ` Brad Laue
2003-04-23 15:25 ` Peter Ruskin
2003-04-23 18:18 ` Paul de Vrieze
2003-04-22 14:26 ` Dan Armak
2003-04-22 14:57 ` Peter Ruskin
2003-04-22 15:40 ` Tony Clark
2003-04-22 15:45 ` Ragnar Hojland Espinosa
2003-04-22 16:00 ` Klavs Klavsen
2003-04-22 16:14 ` Tony Clark
2003-04-22 16:23 ` William Hubbs
2003-04-22 16:59 ` Jon Portnoy
2003-04-22 17:55 ` Mark Bainter
2003-04-22 18:00 ` Klavs Klavsen
2003-04-22 18:06 ` Jon Portnoy
2003-04-25 16:58 ` Brad Laue
2003-04-25 17:31 ` foser
2003-04-25 21:03 ` Brad Laue
2003-04-26 0:38 ` foser
2003-04-22 19:11 ` Fredrik Jagenheim
2003-04-22 23:53 ` Fernand Albarracin
2003-04-22 15:57 ` Brian Jackson
2003-04-22 22:07 ` Brian Jackson
2003-04-22 22:36 ` Robin H.Johnson
2003-04-23 7:43 ` Mark Gordon
2003-04-23 12:46 ` Jon Portnoy
[not found] ` <20030425134659.I30851@leftmind.net>
2003-04-25 21:59 ` Robin H.Johnson
2003-04-23 2:56 ` Brian Jackson
2003-04-23 15:27 ` Peter Fein [this message]
2003-04-23 15:38 ` Grant Goodyear
2003-04-24 18:20 ` Brian Jackson
2003-04-23 5:47 ` Thomas Arnhold
-- strict thread matches above, loose matches on Subject: below --
2003-04-24 0:32 Stroller
2003-04-24 3:50 ` George Shapovalov
2003-04-25 1:01 Stroller
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=20030423102700.5c720818.pfein@pobox.com \
--to=pfein@pobox.com \
--cc=brian@mdrx.com \
--cc=gentoo-dev@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