Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 4534] use ARCHITECTURE instead of ARCH for cache names

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT metalab.unc.edu
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 4534] use ARCHITECTURE instead of ARCH for cache names
  • Date: Sat, 7 Aug 2004 21:16:00 -0400

http://bugs.sourcemage.org/show_bug.cgi?id=4534





------- Additional Comments From acedit AT armory.com 2004-08-07 21:15 -------
The concern I have with suddenly changing the naming sheme for tarballs is
that of backwards compatibility. When we used to look for one thing we could
end up with a number of different values and places to look. So we'd have
to look harder for caches to maintain backwards compatibility.
This is the dreaded "do what I want" pitfall and undoubtedly we'll end
up doing something wrong at some point, or our predefined descisions
will disagree with someone elses interpritation of the right thing to do
(more bugs for me).

A much simpler, and possibly more powerful solution is to allow the user to
set a custom "CACHE_ROOT" variable and store caches whereever they want.

That addresses the heterogenity problem nicely because the user then has the
power to divide caches in whatever way that fits best for them, rather than
us making more arbitrary choices on their behalf. Under this scheme its now
possible to differentiate tarballs based on things other than architecture,
such as optimization flags. You could for example have seperate pools for
statically and dynamically compiled things, or whatever granularity you
care about.

This is also a very simple fix, all I'd have to do is add a menu item
to override the variable.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.




Archive powered by MHonArc 2.6.24.

Top of Page