<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:23:25 JST 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>PFS-JIRA</title>
    <link>https://pfspipe.ipmu.jp/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.3.4</version>
        <build-number>803005</build-number>
        <build-date>13-09-2019</build-date>
    </build-info>


<item>
            <title>[INSTRM-285] Change ICS_ROOT from fixed string to on-invoke generation</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-285</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;(Not a task/bug, but as proposal for change)&lt;/p&gt;

&lt;p&gt;For now, bootstrap sets a path name of installation into ics_config/ups/ics_config.table as a fixed value (like below), for globally used variable over entire ICS actors and scripts.&lt;br/&gt;
&amp;gt; envSet(ICS_MHS_ROOT, &quot;%(ICS_ROOT)&quot;)&lt;/p&gt;

&lt;p&gt;EUPS sets some environment values like EUPS_DEFAULT_DIR, which are generated and set based on ICS_ROOT if you fleshly installed eups and actors using bootstrap. (If you already have any installation of eups, and points a new install target, these will be different.)&lt;br/&gt;
For the production and most of development sites/computers, we will not install eups in a separated way, and mostly we will follow the default way/settings as in the bootstrap.&lt;/p&gt;

&lt;p&gt;So, we could be possible to modify a line above as a generated value but not static. &lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;dependency from actors to ics_config will not change, since we define ics_config as a configuration repository for actors.&lt;/li&gt;
	&lt;li&gt;ics_config.table will be tracked by git, it might be difficult to set customized directory in ics_config.table for e.g. &apos;ICS_MHS_DATA_ROOT&apos;, but we can deal with symlink for them (even for now).&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="12053">INSTRM-285</key>
            <summary>Change ICS_ROOT from fixed string to on-invoke generation</summary>
                <type id="3" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10518&amp;avatarType=issuetype">Task</type>
                                            <priority id="10000" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/medium.svg">Normal</priority>
                        <status id="1" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="atsushi.shimono">shimono</reporter>
                        <labels>
                    </labels>
                <created>Thu, 25 Jan 2018 07:39:41 +0000</created>
                <updated>Thu, 25 Jan 2018 07:39:42 +0000</updated>
                            <resolved>Thu, 25 Jan 2018 07:39:35 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>0</watches>
                                                                    <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="12049">INSTRM-283</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10500" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|ii03un:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>