public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Riyad Kalla" <rsk@u.arizona.edu>
To: <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] portage.py hacking
Date: Thu, 29 May 2003 10:21:31 -0700	[thread overview]
Message-ID: <002001c32606$bf281440$d628c480@rskwork> (raw)
In-Reply-To: <200305291220.20424.khindenburg@cherrynebula.net>

It'll put hair on your chest!

-----Original Message-----
From: Kurt V. Hindenburg [mailto:khindenburg@cherrynebula.net] 
Sent: Thursday, May 29, 2003 10:20 AM
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] portage.py hacking 


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm hacking portage.py to handle multiple DISTDIRS.  Mainly this is in 
the 'fetch' routine; which happens to be over 200 lines.  I notice 
this thoughout portage.py.  This is yucky!!
Somewhere over the years, I heard routines shouldn't be longer than a 
screen page.  Regardless, 100-200+ lines per routine is ridiculous.  
Sigh...it makes hacking so much more irrating... ;-((

- -- 

 Kurt
- ---
  There is no good and evil; there is only power.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+1kFT0cAvx3ELfKARAhKtAKCI6zsGMECmSV0/02xsXZGotGML9ACfY6PJ
g+RJkKrQefYg7B8lyhmzfkI=
=tFoN
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-05-29 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-29 17:20 [gentoo-dev] portage.py hacking Kurt V. Hindenburg
2003-05-29 17:21 ` Riyad Kalla [this message]
2003-05-29 20:54   ` Daniel Armyr
2003-05-29 23:23     ` Luke Graham

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='002001c32606$bf281440$d628c480@rskwork' \
    --to=rsk@u.arizona.edu \
    --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