<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I have applied this patch. Going forward, development of
GetComponents will be done on GitHub.<br>
<br>
Eric<br>
<br>
<blockquote style="border: 0px none;"
cite="mid:AANLkTimxLapTUOMOFDP_aDZYReCy35jNx+pD9ALNjmWj@mail.gmail.com"
type="cite">
<div style="margin-left: 40px;">
<hr style="border-width: 1px 0pt 0pt; border-style: dotted none
none; border-color: rgb(181, 181, 181) -moz-use-text-color
-moz-use-text-color; height: 1px; margin: 0pt;"
class="__pbConvHr"><br>
</div>
<table style="padding-top: 5px;" class="__pbConvTable">
<tbody>
<tr>
<td valign="top"><img
src="cid:part1.04020507.02050005@eseidel.org"
photoaddress="schnetter@cct.lsu.edu" photoname="Erik
Schnetter" name="compose-unknown-contact.jpg"
height="29px" width="29px"></td>
<td style="padding-left: 5px;" valign="top"><a
moz-do-not-send="true"
href="mailto:schnetter@cct.lsu.edu" style="color: rgb(0,
136, 204) ! important; text-decoration: none !
important;">Erik Schnetter</a><br>
<font color="#888888">December 23, 2010 1:31 PM</font></td>
</tr>
</tbody>
</table>
<div style="color: rgb(136, 136, 136); margin-left: 40px;"
__pbrmquotes="true" class="__pbConvBody"><br>
<div><!----><br>
Shouldn't the binary live directly in
Cactus/bin/GetComponents? The<br>
CRL repository would live in repos, as usual, and the binary
itself<br>
would be a symbolic link. We can then do the same with
SimFactory.<br>
<br>
-erik<br>
<br>
</div>
<hr style="border-width: 1px 0pt 0pt; border-style: dotted none
none; border-color: rgb(181, 181, 181) -moz-use-text-color
-moz-use-text-color; height: 1px; margin: 15px 0pt 0pt;"
class="__pbConvHr"><br>
</div>
<table style="padding-top: 5px;" class="__pbConvTable">
<tbody>
<tr>
<td valign="top"><img
src="cid:part2.05070404.03000309@eseidel.org"
photoaddress="eric@eseidel.org" photoname="Eric Seidel"
name="postbox-contact.jpg" height="29px" width="29px"></td>
<td style="padding-left: 5px;" valign="top"><a
moz-do-not-send="true" href="mailto:eric@eseidel.org"
style="color: rgb(0, 136, 204) ! important;
text-decoration: none ! important;">Eric Seidel</a><br>
<font color="#888888">December 23, 2010 1:25 PM</font></td>
</tr>
</tbody>
</table>
<div style="color: rgb(136, 136, 136); margin-left: 40px;"
__pbrmquotes="true" class="__pbConvBody"><br>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<br>
I made the necessary modifications to GetComponents in svn to
support this. I have attached a modified patch to add the git
version of GetComponents, which I would like to apply to finally
complete the transition. GetComponents will now live at <a
moz-do-not-send="true"
href="https://github.com/gridaphobe/CRL"
class="moz-txt-link-freetext">https://github.com/gridaphobe/CRL</a>,
and I will add a LaTeX version of the documentation shortly so
that it can be built with the rest of the Cactus documentation.<br>
<br>
The transition will be a two step process (assuming you are
using the development version): the next time you update Cactus,
you will get the updated thornlist and svn-GetComponents. Then
when you run GetComponents again, it will add the git version,
which will be located in Cactus/bin/CRL/GetComponents. This
seems to be the most stable process to me.<br>
<br>
Eric<br>
<hr style="border-width: 1px 0pt 0pt; border-style: dotted none
none; border-color: rgb(181, 181, 181) -moz-use-text-color
-moz-use-text-color; height: 1px; margin: 15px 0pt 0pt;"
class="__pbConvHr"><br>
</div>
<table style="padding-top: 5px;" class="__pbConvTable">
<tbody>
<tr>
<td valign="top"><img
src="cid:part1.04020507.02050005@eseidel.org"
photoaddress="schnetter@cct.lsu.edu" photoname="Erik
Schnetter" name="compose-unknown-contact.jpg"
height="29px" width="29px"></td>
<td style="padding-left: 5px;" valign="top"><a
moz-do-not-send="true"
href="mailto:schnetter@cct.lsu.edu" style="color: rgb(0,
136, 204) ! important; text-decoration: none !
important;">Erik Schnetter</a><br>
<font color="#888888">December 5, 2010 5:09 PM</font></td>
</tr>
</tbody>
</table>
<div style="color: rgb(136, 136, 136); margin-left: 40px;"
__pbrmquotes="true" class="__pbConvBody"><br>
<pre wrap="">On Sat, Dec 4, 2010 at 12:26 PM, Eric Seidel <a class="moz-txt-link-rfc2396E" href="mailto:eric@eseidel.org"><eric@eseidel.org></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Erik Schnetter wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Ah, I think I misunderstood. I thought you wanted to have a link to
the GetComponents script itself in the Cactus directory. Yes, a link
to the CRL directory makes sense; this is the "standard" way we handle
git repositories at the moment.
</pre>
</blockquote>
<pre wrap="">So I just looked into this, and it seems that GetComponents is not currently
equipped to symlink an entire git repo. This is a silly oversight on my
part; I can fix it, but that would require another patch to GetComponents.
Another possibility would be to create the 'bin' directory and link
GetComponents into bin. Then users could call './bin/GetComponents' or
possibly './bin/CRL/GetComponents', the latter would allow for documentation
to be linked as well.
</pre>
</blockquote>
<pre wrap=""><!---->
I suggest to do both, to correct the fact that GetComponents cannot
link whole repositories, and to create and use a "bin" directory in
Cactus.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">You could create a new project. Better now than later...
"GetComponents" is a rather specific name and limits the scope of the
project.
</pre>
</blockquote>
<pre wrap="">It is easier to just change the name of the project to CRL. This would
change the URL to <a class="moz-txt-link-freetext" href="http://github.com/gridaphobe/CRL">http://github.com/gridaphobe/CRL</a>. If I do this it would
probably make sense to change the URL on my website as well; however, I know
that ET and possibly cactuscode.org link to my website. Are there any other
pages that link to it?
</pre>
</blockquote>
<pre wrap=""><!---->
I don't know. You can set up a permanent redirect on your web server,
which will automatically forward people plus leave a log entry on your
server telling you which pages to correct.
-erik
</pre>
<hr style="border-width: 1px 0pt 0pt; border-style: dotted none
none; border-color: rgb(181, 181, 181) -moz-use-text-color
-moz-use-text-color; height: 1px; margin: 15px 0pt 0pt;"
class="__pbConvHr"><br>
</div>
<table style="padding-top: 5px;" class="__pbConvTable">
<tbody>
<tr>
<td valign="top"><img
src="cid:part2.05070404.03000309@eseidel.org"
photoaddress="eric@eseidel.org" photoname="Eric Seidel"
name="postbox-contact.jpg" height="29px" width="29px"></td>
<td style="padding-left: 5px;" valign="top"><a
moz-do-not-send="true" href="mailto:eric@eseidel.org"
style="color: rgb(0, 136, 204) ! important;
text-decoration: none ! important;">Eric Seidel</a><br>
<font color="#888888">December 4, 2010 11:26 AM</font></td>
</tr>
</tbody>
</table>
<div style="color: rgb(136, 136, 136); margin-left: 40px;"
__pbrmquotes="true" class="__pbConvBody"><br>
Erik Schnetter wrote:
<br>
<blockquote type="cite">Ah, I think I misunderstood. I thought
you wanted to have a link to
<br>
the GetComponents script itself in the Cactus directory. Yes,
a link
<br>
to the CRL directory makes sense; this is the "standard" way
we handle
<br>
git repositories at the moment.
<br>
</blockquote>
So I just looked into this, and it seems that GetComponents is
not currently equipped to symlink an entire git repo. This is a
silly oversight on my part; I can fix it, but that would require
another patch to GetComponents. Another possibility would be to
create the 'bin' directory and link GetComponents into bin. Then
users could call './bin/GetComponents' or possibly
'./bin/CRL/GetComponents', the latter would allow for
documentation to be linked as well.
<br>
<blockquote type="cite">You could create a new project. Better
now than later...
<br>
"GetComponents" is a rather specific name and limits the scope
of the
<br>
project.
<br>
</blockquote>
It is easier to just change the name of the project to CRL. This
would change the URL to <a class="moz-txt-link-freetext" href="http://github.com/gridaphobe/CRL">http://github.com/gridaphobe/CRL</a>. If I
do this it would probably make sense to change the URL on my
website as well; however, I know that ET and possibly
cactuscode.org link to my website. Are there any other pages
that link to it?
<br>
<br>
Eric
<br>
<hr style="border-width: 1px 0pt 0pt; border-style: dotted none
none; border-color: rgb(181, 181, 181) -moz-use-text-color
-moz-use-text-color; height: 1px; margin: 15px 0pt 0pt;"
class="__pbConvHr"><br>
</div>
<table style="padding-top: 5px;" class="__pbConvTable">
<tbody>
<tr>
<td valign="top"><img
src="cid:part1.04020507.02050005@eseidel.org"
photoaddress="schnetter@cct.lsu.edu" photoname="Erik
Schnetter" name="compose-unknown-contact.jpg"
height="29px" width="29px"></td>
<td style="padding-left: 5px;" valign="top"><a
moz-do-not-send="true"
href="mailto:schnetter@cct.lsu.edu" style="color: rgb(0,
136, 204) ! important; text-decoration: none !
important;">Erik Schnetter</a><br>
<font color="#888888">December 2, 2010 9:40 AM</font></td>
</tr>
</tbody>
</table>
<div style="color: rgb(136, 136, 136); margin-left: 40px;"
__pbrmquotes="true" class="__pbConvBody"><br>
<pre wrap="">On Thu, Dec 2, 2010 at 10:35 AM, Eric Seidel <a class="moz-txt-link-rfc2396E" href="mailto:eric@eseidel.org"><eric@eseidel.org></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Frank Loeffler wrote:
On Thu, Dec 02, 2010 at 08:25:12AM -0500, Erik Schnetter wrote:
I think GetComponents
should be handled in the same way, and would omit the symlink.
I wouldn't know how to do that without just coping GetComponents and not
having it in a repository.
As Frank said, this would not be possible with the way GetComponents handles
git repositories. We would have to symlink GetComponents (or a "CRL"
directory). I'm not particularly happy with the way this is handled by
GetComponents, and I've been thinking about modifying the behavior to place
the actual repo in !TARGET unless something is specified in !CHECKOUT, but
that is another discussion...
</pre>
</blockquote>
<pre wrap=""><!---->
Ah, I think I misunderstood. I thought you wanted to have a link to
the GetComponents script itself in the Cactus directory. Yes, a link
to the CRL directory makes sense; this is the "standard" way we handle
git repositories at the moment.
</pre>
<blockquote type="cite">
<pre wrap="">As to Erik's suggestion of placing everything in a single "CRL" directory,
that would actually be a more sensible name for the git repository. It also
holds my experimental generateCRL script, which generates a component list
based on the items you have checked out (only works with cvs and svn so
far). I don't know if GitHub allows you to change the name of your
repository, but I might change it if they do.
</pre>
</blockquote>
<pre wrap=""><!---->
You could create a new project. Better now than later...
"GetComponents" is a rather specific name and limits the scope of the
project.
-erik
</pre>
</div>
</blockquote>
</body>
</html>