[Scons-dev] User Guide and Other Release Documents
Bill Deegan
bill at baddogconsulting.com
Sun Apr 17 11:13:32 EDT 2016
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 <tshortik at gmx.de> 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 at scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20160417/d4dc6359/attachment.html>
More information about the Scons-dev
mailing list