Comments you submit will be routed for moderation. If you have an account, please log in first.

Ticket #3225 (closed enhancement: wontfix)

Opened 12 years ago

Last modified 10 years ago

Setup separate files for TPL

Reported by: wehart Owned by: wehart
Priority: minor Milestone: Acro 2.1
Component: TPL Version:
Keywords: Cc: briadam, lafisk
Subcomponent: Third-party Tools


This will help minimize changes to the acro/


Change History

comment:1 Changed 10 years ago by wehart

  • Version changed from 1.0 to acro 1.0.2
  • Component changed from acro to TPL
  • Milestone set to acro 2.0

comment:2 Changed 10 years ago by jdsiiro

  • Priority changed from high to normal
  • severity normal deleted

Converting all severities into priorities and deprecating the severity field.

comment:3 Changed 10 years ago by wehart

  • Cc briadam, lafisk added
  • Priority changed from normal to minor
  • Type changed from defect to enhancement

I'm reducing the priority on this, because I don't think that this is really a feasible goal. If we created a setup for TPL, then we'd need to manage it more like Acro: we'd have tpl-pico for acro-pico, and tpl-dakota for acro-dakota, etc. This sounds like more of a hassle than it's worth.

An alternative is to have every TPL support its own If we did that, we could still aspire to share TPLs with DAKOTA more transparently.

Any thoughts...?

comment:4 Changed 10 years ago by wehart

  • Version acro 1.0.2 deleted
  • Milestone changed from acro 2.0 to acro 2.1

comment:5 Changed 10 years ago by wehart

  • Status changed from new to closed
  • Resolution set to wontfix

After thinking this through, I don't think that this is really a practical alternative. I'm deleting this, and we can work on simply having Acro and DAKOTA share TPLS. How we configure them is somewhat immaterial.


Add a comment

Modify Ticket

Change Properties
<Author field>
as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.