Jacque, Richard, et al:
Let me ask this another way:
Is it possible to distribute a source stack for other developers to
use to build a standalone in a single format that can be used by all
versions of the Distribution Builder?
If build settings are included in the source stack, older
Rob Cozens wrote:
Is it possible to distribute a source stack for other developers to
use to build a standalone in a single format that can be used by all
versions of the Distribution Builder?
If build settings are included in the source stack, older versions of
the Distribution Builder
All,
Is it possible to distribute a source stack for other developers
to use to build a standalone in a single format that can be used by
all versions of the Distribution Builder?
Best I've come up with
1. Add DB settings to current-format stack.
2. Convert stack to Legacy format.
3. Ship
Richard, et al:
Consider the number of potentially affected users: the subset of
Rev users still using only older versions,
If the issue were simply that developers have not chosen to upgrade
to current-format versions, I would ignore the issue and release all
stacks in the current
Rob Cozens wrote:
Consider the number of potentially affected users: the subset of
Rev users still using only older versions,
If the issue were simply that developers have not chosen to upgrade
to current-format versions, I would ignore the issue and release all
stacks in the current
Hi All,
New issue:
Standalone settings for Legacy stacks are stored in separate Config
stacks, while those settings are internal in the current stack format.
If one is distributing a stack to be used by developers to build
standalones (eg: SDB_Server, SDB_Utilities):
* If saved in legacy
Rob Cozens wrote:
Standalone settings for Legacy stacks are stored in separate Config
stacks, while those settings are internal in the current stack format.
If one is distributing a stack to be used by developers to build
standalones (eg: SDB_Server, SDB_Utilities):
* If saved in legacy
Hi Richard,
AFAIK the standalone settings are stored in custom properties, and
do not rely on anything specific to the new format for storage.
First, let's make sure we're talking apples apples: by standalone
settings, I am referring to the standalone build settings:
platform(s) to build
Rob Cozens wrote:
In Legacy format versions of RunRev, Build Distribution saves the
settings in [stack name] Config.rev, NOT in the source stack itself.
So Build Distribution in Legacy format versions expects to find the
distribution settings in a separate Config stack and the post-Legacy
This preference doesn't seem to get applied, here. I've had it set
since the feature appeared in the ope-beta, and now in 2.8.1 gm-1
Studio, but all stacks get saved as 2.7, anyway.
It's bugzilla'd as bug 4695 pending.
Mac PB G4, OS 10.4.9
Mark
On 5 Jun 2007, at 18:59, J. Landman Gay
Bless you, Jacque!
I don't think there is such a property, but you can read the binary
file to see the format. If it starts with REVO then it is the new
format. But for what you are doing, I don't think you'll have to
resort to this.
Thanks to you it was simple for me to create a menuItem
Rob Cozens wrote:
Go to preferences, Files and memory pane, and turn off the option
that automatically adds the .rev extension. Also turn on the option
in the same pane that preserves the stack file type when saving a
legacy stack.
Thanks.
I guess this is broken, as per a recent list
Hi All,
In setting up an SDBII demo for interested parties I have run into
the need to distribute stacks in Legacy format so the software can be
used by Linux developers.
Working in RRv2.7+ and building distribution downloads in Legacy
format cries out for: developers' handlers to:
1.
Rob Cozens wrote:
Hi All,
In setting up an SDBII demo for interested parties I have run into the
need to distribute stacks in Legacy format so the software can be used
by Linux developers.
Working in RRv2.7+ and building distribution downloads in Legacy format
cries out for: developers'
14 matches
Mail list logo
