Re: [Scons-dev] User Guide and Other Release Documents

2016-04-17 Thread Bill Deegan 
Dirk,

Ideally (but not mandatory) the paths would be uniform across all users
building the packages.
(It's a nice to have)

Aren't the gettext tools needed for the test suite already?

-Bill

On Sun, Apr 17, 2016 at 2:02 AM, Dirk Bächle  wrote:

> Hi Bill,
>
> On 17.04.2016 01:13, Bill Deegan wrote:
>
>> Dirk,
>>
>> Is it fairly simple to replace that text so all the paths are uniform?
>> (As part of the build process?)
>>
>>
> I think I still don't quite understand your intentions. If we make the
> text part of the build process, the paths can change anytime...depending on
> who is creating the release and its packages.
> From what William said, this appears to confuse (some) users and might be
> unwanted.
>
> If you want to have a text that does *not* change, you can hardcode
> it...like it is now.
>
> Best regards,
>
> Dirk
>
> P.S.: Note also that adding proper SconsExample tags to the "gettext"
> documentation would pull the "gettext" tools in as additional dependencies
> for the build process...
>
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] User Guide and Other Release Documents

2016-04-16 Thread William Blevins 
If they were hard coded by the original author then its fine. I was assumed
they hadn't been rebuilt since his 2.4.1 changes. I suppose that is his
Easter Egg.

On Sun, Apr 17, 2016 at 12:13 AM, Bill Deegan 
wrote:

> Dirk,
>
> Is it fairly simple to replace that text so all the paths are uniform?
> (As part of the build process?)
>
> Thanks,
> Bill
>
> On Sat, Apr 16, 2016 at 2:26 PM, Dirk Bächle  wrote:
>
>> William,
>>
>> On 16.04.2016 22:43, William Blevins wrote:
>>
>>> Bill,
>>>
>>> http://scons.org/doc/production/HTML/scons-user.html
>>>
>>> Just search for ptomulik; it's everywhere.
>>>
>>>
>> I count 6 occurrences...which doesn't qualify as "everywhere" to me. ;)
>> Even more important, those strings are simply given in the source
>> documentation file "gettext.xml". So it's not that the doc toolchain
>> replaced some placeholder with the user's home directory by mistake, it's
>> how the author of those lines intended the example to look like. Everything
>> is as it should be...
>>
>> I hope this lets you sleep well. ;)
>>
>> Best regards,
>>
>> Dirk
>>
>>
>> ___
>> Scons-dev mailing list
>> Scons-dev@scons.org
>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>
>
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] User Guide and Other Release Documents

2016-04-16 Thread Bill Deegan 
Dirk,

Is it fairly simple to replace that text so all the paths are uniform?
(As part of the build process?)

Thanks,
Bill

On Sat, Apr 16, 2016 at 2:26 PM, Dirk Bächle  wrote:

> William,
>
> On 16.04.2016 22:43, William Blevins wrote:
>
>> Bill,
>>
>> http://scons.org/doc/production/HTML/scons-user.html
>>
>> Just search for ptomulik; it's everywhere.
>>
>>
> I count 6 occurrences...which doesn't qualify as "everywhere" to me. ;)
> Even more important, those strings are simply given in the source
> documentation file "gettext.xml". So it's not that the doc toolchain
> replaced some placeholder with the user's home directory by mistake, it's
> how the author of those lines intended the example to look like. Everything
> is as it should be...
>
> I hope this lets you sleep well. ;)
>
> Best regards,
>
> Dirk
>
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] User Guide and Other Release Documents

2016-04-16 Thread Dirk Bächle 

William,

On 16.04.2016 22:43, William Blevins wrote:

Bill,

http://scons.org/doc/production/HTML/scons-user.html

Just search for ptomulik; it's everywhere.



I count 6 occurrences...which doesn't qualify as "everywhere" to me. ;)
Even more important, those strings are simply given in the source documentation file "gettext.xml". So it's not that the doc 
toolchain replaced some placeholder with the user's home directory by mistake, it's how the author of those lines intended the 
example to look like. Everything is as it should be...


I hope this lets you sleep well. ;)

Best regards,

Dirk

___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] User Guide and Other Release Documents

2016-04-16 Thread William Blevins 
Bill,

http://scons.org/doc/production/HTML/scons-user.html

Just search for ptomulik; it's everywhere.

V/R,
William

On Sat, Apr 16, 2016 at 5:59 PM, Bill Deegan 
wrote:

> William,
>
> Can you point me to a specific URL so I can investigate?
> It should regenerate on each build.
> The path I would expect to see should start with "/scons"
>
> -Bill
>
> On Sat, Apr 16, 2016 at 9:30 AM, William Blevins 
> wrote:
>
>> Bill,
>>
>> It looks like the SCons 2.5.0 User Guide wasn't rebuilt on the release
>> server because the examples have ptomulik in the directory paths. I'm not
>> sure if this is an issue or not, but shouldn't our release system always
>> regenerate the documentation? This is a bit worrisome because it suggests
>> that documentation releases may be inconsistent.
>>
>> V/R,
>> William
>>
>> ___
>> Scons-dev mailing list
>> Scons-dev@scons.org
>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>
>>
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

[Scons-dev] User Guide and Other Release Documents

2016-04-16 Thread William Blevins 
Bill,

It looks like the SCons 2.5.0 User Guide wasn't rebuilt on the release
server because the examples have ptomulik in the directory paths. I'm not
sure if this is an issue or not, but shouldn't our release system always
regenerate the documentation? This is a bit worrisome because it suggests
that documentation releases may be inconsistent.

V/R,
William
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev