From: "W. Trevor King" <wking@tremily.us>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] More proposed Catalyst changes
Date: Thu, 31 Jan 2013 14:46:53 -0500 [thread overview]
Message-ID: <20130131194653.GA4540@odin.tremily.us> (raw)
In-Reply-To: <20130131183922.GA3946@odin.tremily.us>
[-- Attachment #1: Type: text/plain, Size: 7886 bytes --]
On Thu, Jan 31, 2013 at 01:39:22PM -0500, W. Trevor King wrote:
> I'll see if I can get through 968d818, … sometime later today.
I had a second wind ;). Here are some comments on the remaining
commits:
968d818 Initial creation of a defaults file. Split out hash and contents to their own classes, files
After this, it's not clear to me what the difference is between
catalyst.support and catalyst.util. Perhaps they should be merged.
I'd also use catalyst.targets.__all__ instead of coding a list of
targets in the apparently unrelated
catalyst.defaults.valid_build_targets.
a4ef493 re-version to "git-rewrite branch"
Why?
9d752a7 move confdefaults out of main.py
Looks good, except, I'm not sure why you changed from
`confdefaults.keys()` to `list(confdefaults)` in parse_config() (which
should probably be living in catalyst.config anyway).
c303dae some options cleanup, unifying their use, reducing redundancy.
While I like the general thrust of this, I'd be happier with explicit
boolean options instead of a set of boolean options. For example:
confdefaults = {
'autoresume': False,
'ccache': False,
…
}
6aeb5e3 Move LockInUse from support.py to lock.py, fix bad execption raising, pyflakes cleanup
With respect to the exception raising, see my comments on 63a25eb in
the previous email. Ahh, it looks like you finish that off with
04068a1.
04068a1 massive pyflakes import cleanup and broken CatalystError calls
A lot of this is great stuff (Hooray no `import *`!). However, I'd
split the `print_traceback=True` changes out into their own commit (or
just change the default value for CatalystError while you're testing).
It looks like an unrelated change to
catalyst.defaults.required_build_targets snuck into this commit.
The hash_map changes should probably be squashed into the earlier hash
reorganization, rather than going into this commit.
c672887 begin splitting up generic_stage_target into smaller code blocks so snapshot_target does not need to import it since most of it was not used or initialized properly.
I'd shift “so snapshot_target…” into the commit body for a shorter
summary. Not much to say about the code, since I haven't dug though
it yet.
2b29212 some spacing and comment cleanup, etc.
Looks ok.
28888a7 remove redundant /bin/bash additions in cmd() calls
Looks good.
97802b6 clean out the old spawn functions, use subprocess.call() instead
Hooray. Since you're doing this, I'd drop the earlier commits that
referenced this change (e.g. d23d96b and 1b2597e).
624eb0d move base stage and target files to thier own sub-pkg
s/thier/their/
The diff looks good.
5c689a8 update module loading for the new python structure, rename snapshot_target to snapshot
I think I like this. It's good to use __import__. You're missing a
blank line after your import_module docstring summary [1].
I think that the import_module API should match Python 3's
importlib.import_module [2].
669451d fix options being reset by a config file
See my comments on c303dae. We should really be using ConfigParser's
defaults here, instead of rolling our own default system.
f56017b fix missed PURGEONLY changes
This should be squashed into the settings work that caused it.
c5eb7f7 fix mounts, mountmap hardcoding removal, use normpath to fix paths, add some debug print statements, remove clear & purge code from support.py,
Split the long commit summary.
Can we use logging instead of print?
The except (Failure loading " + x + " plugin) should be squashed into
the commit that caused it and be restricted to only catch
ImportErrors.
The mountmap fix for 'proc' → '/proc' should be squashed into the
commit that caused it.
- mypath=self.settings["chroot_path"]
+ #mypath=self.settings["chroot_path"]
Just remove this entirely, don't comment it out.
b2ea321 remove a named parameter in generate_hash() call due to a parameter name change
Move “due to …” into the commit message body.
I think keyword arguments are better, because changes to keywords
usually occur alongside changes to the argument semantics. A keyword
mismatch is an obvious fix, while changes due to a semantic shift can
be more subtle.
a847803 Use normpath from support
Why are we not using os.path.normpath?
Also, remove instead of commenting out.
6108400 chmod +x all sh scripts so they can run from the git checkout
Looks good,
242c17d rename all target .py file and classes without the "_target" so they are the same as the .sh files and work with teh simplified module loading.
Move “so they …” into the commit message body and s/teh/the/.
I was going to suggest this if you hadn't gotten around to it ;).
ecc653f fix targets.sh path
Squash into the commit that caused it.
d563be8 Comment out a small code block causing TypeError, which also was short circuiting another large code block. FIXME!!!! This whole class seems overly complicated with TOO MANY nested try:excepts:
Long commit summary.
I agree that a few of these methods should be split into helper
functions for easier reading.
e05cc34 Break out a few more repeated (path1 + path2)'s to doing it once and using the temp variable. comment out some debug print's
Long commit summary.
os.path.join! Also, convert debug prints to use the logging module
;).
e0738c0 rename a make.conf key to make_conf due to bash variable name restrictions
Squash into causing commit.
db2af17 fix my broken subprocess call to use Popen due to environment passing and return code needs
Squash into causing commit.
ae61e4a reduce 2 operations into one simpler one
Just switch to ConfigParser ;).
b08a757 extend ParserBase to do variable substitution.
ConfigParser does that to ;).
265c8ed add a "shdir" setting to make moving the bash code around easier and have less hardcoded paths in the bash scripts
Long commit summary.
Your comment claims catalyst runtime executables for both sharedir and
shdir.
dc90e40 migrate all target shell scripts to use the new shdir setting
Squash into 265c8ed.
2fa8968 minor cleanup
Squash into earlier (proposed) global whitespace cleanup and import
cleanups.
d7007a9 fix a bug in relative path use. Add some unique identifiers to echo statements to make identifying the source of a message easier.
Split into two commits (relative path, unique identifiers). We should
also try and figure out less arbitrary identifiers.
8b9a1c0 add embedded variable substitiution to default settings
ConfigParser does this.
1259fa6 make shdir a complete path to ease it's use. Add port_config path setting to remove more hard coded paths in code.
Squash shdir stuff into the earlier shdir addition.
Squash port_config into wherever you use it…
923e8a2 remove trailing slash for consistency in variables and remove extra slashes in paths
os.path.join()
55a58ee Add a forced debug print statement in cmd() for better debug output
Python logging.
24d69bd Commit my testpath file with instructions to run the git checkout code directly without being installed.
s/caatalyst/catalyst/
It would also probably be a good idea to add an example test.conf with
relative paths.
b7036f3 update gitignore
As I said earlier, the test.* files your ignoring don't seem to exist
in my checkout.
0fb2609 add archdir to settings
Looks good.
Cheers,
Trevor
[1]: http://www.python.org/dev/peps/pep-0257/#multi-line-docstrings
[2]: http://docs.python.org/dev/library/importlib.html#importlib.import_module
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-31 19:47 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 8:32 [gentoo-catalyst] More proposed Catalyst changes Brian Dolbec
2013-01-08 18:08 ` Peter Stuge
2013-01-12 8:55 ` Brian Dolbec
2013-01-31 18:39 ` W. Trevor King
2013-01-31 19:46 ` W. Trevor King [this message]
2013-02-02 20:41 ` Brian Dolbec
2013-02-03 12:44 ` W. Trevor King
2013-04-11 2:06 ` [gentoo-catalyst] chmod +x all sh scripts so they can run from the git checkout W. Trevor King
2013-02-02 18:45 ` [gentoo-catalyst] More proposed Catalyst changes Brian Dolbec
2013-02-03 12:20 ` W. Trevor King
2013-02-26 18:04 ` [gentoo-catalyst] patch, fix broken seed stage update W. Trevor King
2013-02-27 1:30 ` Brian Dolbec
2013-02-27 1:40 ` W. Trevor King
2013-02-27 2:35 ` Brian Dolbec
2013-02-27 2:41 ` Matt Turner
-- strict thread matches above, loose matches on Subject: below --
2013-02-26 16:20 Brian Dolbec
2013-02-26 16:37 ` W. Trevor King
2013-02-26 16:47 ` Brian Dolbec
2013-02-26 16:48 ` Peter Stuge
2013-02-26 17:29 ` Rick "Zero_Chaos" Farina
2013-02-26 19:39 ` Matt Turner
2013-02-27 2:04 ` Brian Dolbec
2013-02-27 2:37 ` Matt Turner
2013-02-27 12:12 ` W. Trevor King
2013-02-27 2:37 ` Matt Turner
2013-02-27 3:03 ` Brian Dolbec
2013-02-27 3:22 ` Matt Turner
2013-02-27 3:49 ` Brian Dolbec
2013-03-08 17:27 ` [gentoo-catalyst] [PATCH v2] Remove update_seed_command and strengthen update_seed W. Trevor King
2013-03-08 18:34 ` Rick "Zero_Chaos" Farina
2013-03-08 18:47 ` [gentoo-catalyst] [PATCH v3] Strengthen update_seed to update @system and @world with dependencies W. Trevor King
2013-03-08 20:14 ` Matt Turner
2013-03-09 12:10 ` [gentoo-catalyst] " W. Trevor King
2013-04-11 17:09 ` [gentoo-catalyst] Binary package dependencies and update_seed W. Trevor King
2013-04-11 17:39 ` Rick "Zero_Chaos" Farina
2013-04-11 17:52 ` W. Trevor King
2013-04-12 15:12 ` [gentoo-catalyst] [PATCH] files/catalyst.conf: Document linking issues with binary packages W. Trevor King
2013-04-12 15:21 ` Rick "Zero_Chaos" Farina
2013-04-12 15:33 ` W. Trevor King
2013-04-12 16:11 ` Rick "Zero_Chaos" Farina
2013-04-12 18:21 ` [gentoo-catalyst] [PATCH v2 0/2] pkgcache warning in catalyst-config(5) W. Trevor King
2013-04-12 18:21 ` [gentoo-catalyst] [PATCH v2 1/2] doc/catalyst-config.5.txt: Add man page for catalyst.conf W. Trevor King
2013-04-12 18:27 ` [gentoo-catalyst] " W. Trevor King
2013-04-12 18:47 ` [gentoo-catalyst] " Rick "Zero_Chaos" Farina
2013-04-12 19:05 ` W. Trevor King
2013-04-12 19:30 ` Rick "Zero_Chaos" Farina
2013-04-16 1:33 ` [gentoo-catalyst] [PATCH v3 0/2] pkgcache warning in catalyst-config(5) W. Trevor King
2013-04-16 1:33 ` [gentoo-catalyst] [PATCH v3 1/2] doc/catalyst-config.5.txt: Add man page for catalyst.conf W. Trevor King
2013-04-16 1:33 ` [gentoo-catalyst] [PATCH v3 2/2] doc/catalyst-config.5.txt: Document linking issues with binary packages W. Trevor King
2013-12-14 5:41 ` [gentoo-catalyst] Re: [PATCH v3 0/2] pkgcache warning in catalyst-config(5) W. Trevor King
2013-04-12 18:21 ` [gentoo-catalyst] [PATCH v2 2/2] doc/catalyst-config.5.txt: Document linking issues with binary packages W. Trevor King
2013-04-11 18:20 ` [gentoo-catalyst] Binary package dependencies and update_seed Matt Turner
2013-04-11 18:22 ` Matt Turner
2013-04-11 18:53 ` Rick "Zero_Chaos" Farina
2013-04-11 19:00 ` W. Trevor King
2013-04-11 19:03 ` Matt Turner
2013-04-11 19:18 ` Rick "Zero_Chaos" Farina
2013-04-11 20:24 ` Matt Turner
2013-04-11 20:34 ` W. Trevor King
2013-04-12 1:11 ` W. Trevor King
2013-04-11 20:37 ` Rick "Zero_Chaos" Farina
2013-04-11 18:53 ` W. Trevor King
2013-04-12 6:57 ` Brian Dolbec
2013-04-16 19:42 ` [gentoo-catalyst] [PATCH 0/2] Blacklisting binary packages W. Trevor King
2013-04-16 19:42 ` [gentoo-catalyst] [PATCH 1/2] spec: Add binpkg_blacklist option for troublesome packages W. Trevor King
2013-04-16 19:42 ` [gentoo-catalyst] [PATCH 2/2] Revert "don't build packages during update_seed" W. Trevor King
2013-04-16 20:35 ` [gentoo-catalyst] [PATCH 0/2] Blacklisting binary packages Matt Turner
2013-04-16 20:59 ` W. Trevor King
[not found] ` <516DD074.3090906@gentoo.org>
2013-04-16 22:53 ` W. Trevor King
2013-04-17 4:18 ` Brian Dolbec
2013-04-17 11:30 ` W. Trevor King
2013-04-17 14:57 ` Matt Turner
2013-04-19 14:11 ` Rick "Zero_Chaos" Farina
2013-04-19 16:18 ` W. Trevor King
2013-04-19 16:32 ` Rick "Zero_Chaos" Farina
2013-04-19 16:36 ` W. Trevor King
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=20130131194653.GA4540@odin.tremily.us \
--to=wking@tremily.us \
--cc=gentoo-catalyst@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