- changed status to open
- removed comment
make COMPONENTLIST_TARGET 'stable'
Issue #61
closed
Could we remove the 'experimental' tag from COMPONENTLIST_TARGET? I am using this for quite some time now, without trouble. The biggest question might actually be if this is desired to be supported. What are the thoughts?
about COMPONENTLIST_TARGET: This selects a directory where GetComponents will write the used component list to, after downloading lists given by URL, and after combining included component lists. I usually set it like this:
!DEFINE COMPONENTLIST_TARGET = $ROOT/thornlists/
Without COMPONENTLIST_TARGET being set to something, GetComponents will not write the thornlist.
Keyword:
Comments (6)
-
-
reporter
- removed comment
I use them and don't have trouble.
-
- removed comment
Ok then let's go ahead and remove the experimental tag from both features.
-
- removed comment
This issue has been addressed in the Git repository. The svn version will be patched following the ET_2010_11 release.
-
- changed status to resolved
- removed comment
issue resolved in revision 706 of the svn version
-
- edited description
- changed status to closed
- Log in to comment
- Assignee
- Type
- Priority
- Status
- closed
- Component
- GetComponents
- Milestone
- –
- Version
- –
- Votes
- 0
- Watchers
- 0
That would be fine with me. I guess that would also include moving the component list includes to 'stable'? It seems that there wouldn't be much point in writing the component list if it hadn't been modified, unless the original list was specified as a URL. I've never used the includes myself, would you consider them stable?