[sldev] Better build instructions

[Ricky]

Thanks for the enlightenment! :D

If this is common, then the biggest pillar I was standing upon will have
withered away, and we should build distinct articles for each new build
process.

If we do go that route, the neext question is how do we know when to just
tweak the existing article, and when to split a new article? Do we only ever
split? In the case of swithcing from the old build system to CMake, I can
see the logic. But what happens when only one or two dependencies are
changed?  Or if a script is adjusted to make the workflow smoother? Etc.
Large and sudden changes in build system makes it easy to know to make a new
split, but small incremental changes can hurt just as badly after a few of
them come into play.

Ricky

On Fri, Jul 25, 2008 at 1:45 PM, Mike Monkowski <monkowsk at watson.ibm.com>
wrote:

> Ricky wrote:
>
>> 1: If the most common new developer (see note) DOESN'T want to get the
>> latest edition of the code.  I don't understand why they wouldn't...  Maybe
>> some enlightenment for me?
>>
>
> If you want to make a code change and you want to allow many people to use
> it without much hassle, then you want to distribute as little as possible,
> usually only the viewer executable, and let others just drop it into the
> existing installation.  This means the stable version and the release
> candidates and an occasional First Look.
>
> I have never built from the trunk and I don't see any reason I would want
> to. :-)
>
> Mike
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20080725/3fa2d5e6/attachment-0001.htm