From: Ted Kosan <tkosan@yahoo.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] Relative paths in spec files
Date: Mon, 7 Aug 2006 15:58:01 -0700 (PDT) [thread overview]
Message-ID: <20060807225802.27131.qmail@web31809.mail.mud.yahoo.com> (raw)
I am attempting to switch a number of the absolute paths which are present in
my spec files and in my catalyst configuration file into relative paths.
For example, I would like to replace an absolute path like this:
envscript="/home/tkosan/checkouts/jdos/jdos/catalyst_config_files/catalyst-env.sh"
with a relative path like this:
envscript="../catalyst_config_files/catalyst-env.sh"
I have been studying the python code for catalyst_v2.0_rc50. The file_locate
function near line 506 in catalyst_support.py appears to support relative
paths, but the following code that calls this function near line 157 in
generic_stage_target.py seems to be disabling path expansion by setting
"expand" to 0:
<code_snip>
# this next line checks to make sure that the specified variables exist on
disk.
#pdb.set_trace()
file_locate(self.settings,["source_path","snapshot_path","distdir"],expand=0)
# if we are using portage_confdir, check that as well
if self.settings.has_key("portage_confdir"):
file_locate(self.settings,["portage_confdir"],expand=0)
</code_snip>
Is there a way to enable the use of relative paths in the spec files and in the
catalyst configuration file that perhaps I am not aware of?
Thanks in advance :-)
Ted Kosan
tkosan@dev.java.net
--
gentoo-catalyst@gentoo.org mailing list
next reply other threads:[~2006-08-07 22:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 22:58 Ted Kosan [this message]
2006-08-07 23:09 ` [gentoo-catalyst] Relative paths in spec files Andrew Gaffney
2006-08-09 6:07 ` Ted Kosan
2006-08-09 7:39 ` "Andreas Rückert"
2006-08-10 18:11 ` Ted Kosan
2007-06-10 23:25 ` [gentoo-catalyst] " Charles Duffy
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=20060807225802.27131.qmail@web31809.mail.mud.yahoo.com \
--to=tkosan@yahoo.com \
--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