Re: User Guide and Other Release Documents

Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org>
Newsgroups gmane.comp.programming.tools.scons.devel
Message-ID <CAEyG4CFdWAfAxB2WACdCq6vWa6OuYVTcPU4xP4MMDHrN0Uc_7w@mail.gmail.com>
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 <[email protected]> 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
> [email protected]
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>

_______________________________________________
Scons-dev mailing list
[email protected]
https://pairlist2.pair.net/mailman/listinfo/scons-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.