Re: [Scons-dev] packaging tests: tar; and an xz question

So it sounds like if there's native windows tar, then there's no need to check for bzip2 executable for windows to be able to handle .tar.bz2 files? If that's the case then the test should be updated to figure out which tar and if bzip2 is indeed needed to run skip otherwise. Regarding xz, pull

Re: [Scons-dev] Visual Studio without C++ compiler installed

I think the msvc tool should discard versions where there is no cl tool since msvc (should) = Microsoft Visual C Any idea how to update the appveyor config file to have it install cl ? -Bill On Sat, Aug 11, 2018 at 10:03 PM, Daniel Moody wrote: > I was looking at one of our test in the

Re: [Scons-dev] PR 3155

at 8:19 AM, Bill Deegan wrote: > I put some feedback on the PR almost as soon as you submitted it that you > have yet to respond to. > > We need a test which fails under normal scons before your changes and > passes after, as we do with pretty much any and all pull requests. > >

Re: [Scons-dev] PR 3155

I put some feedback on the PR almost as soon as you submitted it that you have yet to respond to. We need a test which fails under normal scons before your changes and passes after, as we do with pretty much any and all pull requests. -Bill On Mon, Jul 23, 2018 at 5:42 PM, Jason Kenny wrote:

Re: [Scons-dev] Should we remove python 3.5 from our CI tests

I have a collection of scripts for building various python versions on ubuntu & centos. Please feel free to use: https://github.com/bdbaddog/python_build_scripts Pull requests welcome. I suppose I could move to scons, but these aren't just for scons. -Bill On Sun, Jul 22, 2018 at 8:39 AM,

Re: [Scons-dev] Should we remove python 3.5 from our CI tests

While neither windows nor MacOS include SCons, there are defacto package managers for both: Windows: Chocolatey - no scons, but multiple python versions MacOS: macports and homebrew (both include scons and multiple python versions Thus far we're not having issues with CI running on 2.7.x, 3.5.x,

Re: [Scons-dev] Should we remove python 3.5 from our CI tests

Pretty certain Gary's with me in saying, SCons will support Python 2.7 and 3.5+ in (at least) the 3.x releases. Most likely through (at least) the end of 2018. I know many who actively participate in SCons community live on the leading edge of OS and Python releases but many users do not. Also,

Re: [Scons-dev] Website Sources to GitHub

Anatoly, What do you mean by "PR interface from GitHub"? Use Travis-ci or some such to build website? Or use something to render the wiki sources onto a "normal" website via travis or buildbot or other? -Bill On Fri, Jul 20, 2018 at 11:38 AM, anatoly techtonik wrote: > On Fri, Jul 20, 2018 at

Re: [Scons-dev] PR 3129

Don't forget there's also: buildbot.scons.org Yes any help resolving failing tests in travis ci and appveyor would be most welcome. -BIll On Wed, May 30, 2018 at 1:53 PM, Daniel Moody wrote: > Master is not passing all tests for Windows, and some tests aren't even > run if the binaries aren't

Re: [Scons-dev] Should we remove python 3.5 from our CI tests

Though it's likely not worth testing both 32 and 64 bit pythons on windows. -Bill On Fri, May 25, 2018 at 4:44 PM, Bill Deegan <b...@baddogconsulting.com> wrote: > We need to test every version we say we support. > That's the purpose of the CI... > > On Fri, May 25, 201

Re: [Scons-dev] Should we remove python 3.5 from our CI tests

We need to test every version we say we support. That's the purpose of the CI... On Fri, May 25, 2018 at 4:10 PM, Mats Wichmann wrote: > On 05/25/2018 02:59 PM, Daniel Moody wrote: > > Opening discussion to remove 3.5 from the CI tests. > > > > Is there any reason we need 3.5

Re: [Scons-dev] CLion

Voted! On Thu, Apr 26, 2018 at 1:13 PM, Jay Sistar via Scons-dev < scons-dev@scons.org> wrote: > I've recently found myself in the position of SCons evangelism. > > The CLion project has very few (less than 200) votes for SCons support. I > believe that support in CLion would grow the usage of

Re: [Scons-dev] Debian and Buildbot

Indeed. (I'm actually on their board of directors as well.. ) We've also got travisCI and Appveyor running on pull requests. The switch to github has been fruitful for sure. (Though they are now supporting bitbucket but not hg) On Mon, Apr 16, 2018 at 2:12 AM, Russel Winder

Re: [Scons-dev] QMTest where_is different than Environment.py Detect

f the PATH in the generated Sconstruct? If not, is it useful for > those tests to fail if the tool is in a non-standard location? > > On Mon, Apr 9, 2018, 11:57 AM Bill Deegan <b...@baddogconsulting.com> > wrote: > >> There is a win32.py in Platform which set's env['PATH'

Re: [Scons-dev] QMTest where_is different than Environment.py Detect

six.py in Platform > which sets up a default path for linux, but for Windows it relies on msvs > tool to setup an environment. There doesn't seem to be a analogous posix.py > for windows. > > > On Mon, Apr 9, 2018, 11:28 AM Bill Deegan <b...@baddogconsulting.com> > wrote:

Re: [Scons-dev] QMTest where_is different than Environment.py Detect

Depends how it is used. If it's used in such a way that the results are then used in a generated SConstruct to specify full path to the tools, then the logic makes sense. If they are used to determine if the test should be run and they yield a path which SCons wouldn't natively find, then yes

[Scons-dev] scons.org website: old scons versions docs temporally offline

They're being restored now and should be back up in 10-15 minutes. -Bill ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] SCons for distributed builds?

Chris, While it does sound like an interesting application, it may be there already exist better tools for this. Are you using Grid Engine or LSF? Or Celery. Those would be the first tools I'd reach for if I'm understanding what you're asking for properly. In general we discuss use models etc

Re: [Scons-dev] Renaming Node's .binfo and .ninfo attributes

>> >> >> >> Jason >> >> >> >> *From:* Scons-dev <scons-dev-boun...@scons.org> *On Behalf Of *Bill >> Deegan >> *Sent:* Wednesday, March 28, 2018 8:22 PM >> *To:* SCons developer list <scons-dev@scons.org> >> *Subject

[Scons-dev] Renaming Node's .binfo and .ninfo attributes

Greetings, I'd like to rename them as follows so they're more easily comprehensible .binfo -> .build_info .ninfo -> .node_info Thoughts? Reasons not to change? Is anyone reaching that far into the Nodes? -Bill ___ Scons-dev mailing list

[Scons-dev] Feedback on issue creation template

Greetings, I've just added an issue creation template to Github. See it here: https://github.com/SCons/scons/blob/master/.github/issue_template.md If you have a moment to take a look and let me know if I've missed any information which should be provided when filing a new issue. Thanks, Bill

[Scons-dev] SCons bug tracking officially moved to Github!

Great news! SCons bug tracking officially moved to Github! After a few missteps we're there. I'm still trying to figure out if we can put tigris' bug tracker in read only mode. All tigris bugs have been migrated and kept their original issue number unless there already existed a pull request

[Scons-dev] Tigris->github migration in progress

Please do not file additional bugs on tigris until further notice. Additionally the scons/scons repo is in read only mode except for maintainers while this migration is in progress. Due to GitHub API call limits this takes a while (started last night at approx 10pm PST and still running) Thanks

Re: [Scons-dev] Migrating issues from Tigris to GitHub

gt; Regards, > Andrew > > On 3 January 2018 at 18:37, Bill Deegan <b...@baddogconsulting.com> wrote: > >> Crap. >> It looks like the migration script overwrote existing pull requests. >> They are all gone and replaced with migrated bugs. >> >&g

[Scons-dev] github scons/scons locked

Greetings, We had some issues with our bug migration and accidently overwrote the existing pull requests. I have a support request into github to see if we can roll it back. I'll keep the repo locked until I get a response. Sorry for the inconvenience. -Bill

Re: [Scons-dev] Migrating issues from Tigris to GitHub

Crap. It looks like the migration script overwrote existing pull requests. They are all gone and replaced with migrated bugs. Let me see if I can get ahold of github and get them restored.. -Bill On Tue, Jan 2, 2018 at 1:39 PM, Bill Deegan <b...@baddogconsulting.com> wrote: > o.k.

Re: [Scons-dev] Migrating issues from Tigris to GitHub

s, which >> in some of the text of our issue, that was not intended. If possible you >> can replace '#[number]' with 'choice [number]' in the text when they get >> reprocessed? >> >> I read about choice here: >> https://github.com/github/markup/issues/303 >&g

Re: [Scons-dev] Migrating issues from Tigris to GitHub

://developer.github.com/v3/issues/#edit-an-issue'} On Mon, Jan 1, 2018 at 8:05 PM, Bill Deegan <b...@baddogconsulting.com> wrote: > No go. > > python tigris2github.py > Traceback (most recent call last): > File "tigris2github.py", line 11, in

Re: [Scons-dev] Migrating issues from Tigris to GitHub

Andrew, Great! I'll see if I can kick off the migration today and start 2018 on a high note! Thanks for all the hard work! -Bill On Mon, Jan 1, 2018 at 6:23 AM, Andrew Featherstone < andrew.featherst...@cantab.net> wrote: > Done. > > On 29 December 2017 at 17:28,

Re: [Scons-dev] Scons github linked to bdbaddog Appveyor account

O.k. I think I did that. Take a look at: On Sun, Dec 31, 2017 at 2:09 PM, Daniel Moody wrote: > Hey Bill, > > It seems that the appveyor account is your account linked to scons, for > example when you check some of our recently added appveyor builds: >

Re: [Scons-dev] Wiki migration from Bitbucket to GitHub

site does want to > keep their links working, then they can update them to point at GitHub. I'd > prefer this to making sure that a blog post from 2010 still points to > content, with no idea that the newer content exists. > > On 21 December 2017 at 22:03, Bill Deegan <b...@ba

Re: [Scons-dev] Migrating issues from Tigris to GitHub

imiting of GitHub. > > Cheers, > Andrew > > On 28 December 2017 at 22:12, Bill Deegan <b...@baddogconsulting.com> > wrote: > >> Yes. Sorry I didn't see the link in the existing markup. >> That looks good to me. >> So to move forward (migrate bugs to scons

Re: [Scons-dev] Migrating issues from Tigris to GitHub

down. As an example, see https://github.com/ajf58/ > tigris-sandbox/issues/6, which has an attachment found at > https://github.com/ajf58/tigris-issue-attachments/blob/master/190/bug6.zip > . > > Have I understood your question correctly? > > Andrew > > On 28 December 20

Re: [Scons-dev] Migrating issues from Tigris to GitHub

rt moving forward with this! > Good work! > > On Dec 28, 2017 2:36 PM, "Andrew Featherstone" < > andrew.featherst...@cantab.net> wrote: > >> Hi All, >> >> Any comments or feedback on this? >> >> Regards, >> Andrew >> &g

Re: [Scons-dev] Wiki migration from Bitbucket to GitHub

ew home page. In an ideal world every page > would return a 301 status code, but alas. > > Andrew > > On 21 December 2017 at 21:35, Bill Deegan <b...@baddogconsulting.com> > wrote: > >> Yup. I thought I'd done that when I did the migration. >> >> Probably

Re: [Scons-dev] Wiki migration from Bitbucket to GitHub

< andrew.featherst...@cantab.net> wrote: > How stupid of me not to look beforehand! Perhaps we could make this > obvious on the BitBucket Wiki at https://bitbucket.org/scons/ > scons/wiki/Home? > > Andrew > > On 21 December 2017 at 21:24, Bill Deegan <b...@baddogconsulting.com>

Re: [Scons-dev] Wiki migration from Bitbucket to GitHub

https://github.com/SCons/scons/wiki On Thu, Dec 21, 2017 at 1:24 PM, Bill Deegan <b...@baddogconsulting.com> wrote: > The wiki's already migrated.. > > On Thu, Dec 21, 2017 at 1:17 PM, Andrew Featherstone < > andrew.featherst...@cantab.net> wrote: > >> Hi All,

Re: [Scons-dev] Wiki migration from Bitbucket to GitHub

The wiki's already migrated.. On Thu, Dec 21, 2017 at 1:17 PM, Andrew Featherstone < andrew.featherst...@cantab.net> wrote: > Hi All, > > I've migrated the wiki from BitBucket to my fork on GitHub. This was > pretty straightforward, with the details in the git history at >

Re: [Scons-dev] CI Roadmap: ( Was Enabling Travis CI service for SCons on github)

es a very > quick failure. > > Andrew > > On 20 December 2017 at 16:39, Bill Deegan <b...@baddogconsulting.com> > wrote: > >> 4. We're already using unittest. QMtest is just the name of the directory >> at this point. (You used to have to install qmtest to run the

Re: [Scons-dev] CI Roadmap: ( Was Enabling Travis CI service for SCons on github)

necessary > to split up tests across jobs. > 4. agreed, a well known standard python testing framework would be great. > I like pytest. > > My goal currently is to at least get basic CI on github working with as > little rework as possible. > > On Wed, Dec 20, 2017 at

[Scons-dev] CI Roadmap: ( Was Enabling Travis CI service for SCons on github)

determined list of all tests >> --interval-end FLOAT Percentile as float (0.0 - 1.0) of what >> test to start on from the >> determined list of all tests >> >> interval-start default is 0 >> interval-end default is 1 >

Re: [Scons-dev] Enabling Travis CI service for SCons on github

list of all tests > > interval-start default is 0 > interval-end default is 1 > > A little more flexible I think. > > > > On Wed, Dec 20, 2017 at 8:41 AM, Bill Deegan <b...@baddogconsulting.com> > wrote: > >> Maybe add a flag directly to runtest.py to

Re: [Scons-dev] Enabling Travis CI service for SCons on github

0.53 > > Currently python 3 will fail from several tests so I have them commented > out. > > > On Wed, Dec 20, 2017 at 8:00 AM, Bill Deegan <b...@baddogconsulting.com> > wrote: > >> Parallel should help. >> >> On my buildbot worker (with 2 other builds

Re: [Scons-dev] Enabling Travis CI service for SCons on github

> Andrew > > On 18 December 2017 at 22:51, Bill Deegan <b...@baddogconsulting.com> > wrote: > >> Daniel, >> >> Can we get travis to test with py2.7, 3.5, and 3.6 ? >> >> -Bill >> >> On Wed, Dec 6, 2017 at 12:03 AM, Bill Deegan <

Re: [Scons-dev] Enabling Travis CI service for SCons on github

Daniel, Can we get travis to test with py2.7, 3.5, and 3.6 ? -Bill On Wed, Dec 6, 2017 at 12:03 AM, Bill Deegan <b...@baddogconsulting.com> wrote: > Thanks! > That's pretty cool. > I'll try to get the coverage hooked up soon. > That'll also be very useful.. > > On Tue

Re: [Scons-dev] Enabling Travis CI service for SCons on github

ojects: > https://github.com/JonathonReinhart/scuba/pull/98 > > Towards the bottom you'll see a "View Details" button. > Clicking that will expand a box showing the results of all the "checks" > that ran. > > > > On Tue, Dec 5, 2017 at 11:13 PM, Bill Deegan &

Re: [Scons-dev] Enabling Travis CI service for SCons on github

om that repo in the > PR. > > You can see it it in one of the PR now and clicking show all checks: > https://github.com/SCons/scons/pull/25 > > > On Tue, Dec 5, 2017 at 11:02 PM, Bill Deegan <b...@baddogconsulting.com> > wrote: > >> Does it build on pull re

Re: [Scons-dev] Enabling Travis CI service for SCons on github

there any private server scons has that could run a small web server >>>> to receive the webhook notification from travis and write the tweet to >>>> twitter? >>>> >>>> For the web server, I was thinking of using a python web server to >>>> receive th

Re: [Scons-dev] Enabling Travis CI service for SCons on github

ld run a small web server to > receive the webhook notification from travis and write the tweet to twitter? > > For the web server, I was thinking of using a python web server to receive > the notification and twython package to write the tweet. > > > > > >

Re: [Scons-dev] Enabling Travis CI service for SCons on github

Code coverage reports using https://github.com/marketplace/coveralls > > At that point can buildbot based tasks be retired? > > Andrew > > > On 5 December 2017 at 18:22, Bill Deegan <b...@baddogconsulting.com> > wrote: > >> Great! >> That's all I can think

Re: [Scons-dev] Enabling Travis CI service for SCons on github

r Twitter messages with some setup. > > Any other notification types we are interested in? > > I'll take a look and submit a PR. > > On Dec 5, 2017 12:55 PM, "Bill Deegan" <b...@baddogconsulting.com> wrote: > >> Should be enabled now. >> Just merged o

Re: [Scons-dev] Enabling Travis CI service for SCons on github

Should be enabled now. Just merged one of your pull requests.. I'll keep an eye on it. Can we get the results to post on twitter? and/or IRC? On Sun, Dec 3, 2017 at 9:08 PM, Bill Deegan <b...@baddogconsulting.com> wrote: > Yes. I'll get to it in the next week or so. > We do have bu

[Scons-dev] Bug migration to GitHub.

ssues into my fork on GitHub. > Perhaps I should move this separate topic onto the scons-dev mailing list? > > Andrew > > On Mon, 04 Dec 2017 05:06:54 -, Bill Deegan <b...@baddogconsulting.com> > wrote: > > Yes. that's the plan. > Just no one working on it at the m

Re: [Scons-dev] Enabling Travis CI service for SCons on github

Yes. I'll get to it in the next week or so. We do have buildbot doing similar at : buildbot.scons.org -Bill On Sun, Dec 3, 2017 at 2:02 PM, Daniel Moody wrote: > In this pull request: > https://github.com/SCons/scons/pull/17 > > SCons got a Travis CI script added to the

Re: [Scons-dev] [Scons-users] Github Project renamed from SConsProject to SCons

> This should probably be killed: > https://bitbucket.org/scons/scons-pelican-bootstrap3 > > On Wed, Nov 22, 2017 at 10:00 PM, Bill Deegan <b...@baddogconsulting.com> > wrote: > > > > > > On Wed, Nov 22, 2017 at 9:46 AM, Bassem Girgis <brgir...@gmail.com&

Re: [Scons-dev] [Scons-users] Github Project renamed from SConsProject to SCons

came out, which saved me untold hours (or >> days or weeks) of converting our build system, some parts of which are >> almost 20 years old now. >> >> Eric >> >> On Wed, Nov 22, 2017 at 7:11 AM, Bill Deegan <b...@baddogconsulting.com> >> wrote: >

[Scons-dev] Github Project renamed from SConsProject to SCons

ke sure they are all pointing at the proper (changed) URLs. -Bill Deegan SCons Project Co-Manager ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev

[Scons-dev] Error running doc-validate.py

Dirk, Any idea? It seems to validate o.k. on my other machine, but not on the machine I use for releases. Errors below. 62.91% (134/213) doc/man/scons.xml Element '{http://www.scons.org/dbxsd/v1.0}listitem': Character content other than whitespace is not allowed because the content type is

Re: [Scons-dev] Hashes

Indeed. SCons is not(currently) in the business of providing security assured builds. (Nor as far as I know is any other build system, though I keep finding new ones I'd never heard of or that are getting released to the public from being strictly internal tools (google..)) Just correct builds.

Re: [Scons-dev] TestingMethodology Wiki link broken

found it. fixed. On Thu, Oct 12, 2017 at 5:53 AM, Bill Deegan <b...@baddogconsulting.com> wrote: > https://github.com/SConsProject/scons/wiki/TestingMethodology > > Where's the link from? (What page) > > On Wed, Oct 11, 2017 at 8:33 PM, Daniel Moody <dmoody...@gmai

Re: [Scons-dev] TestingMethodology Wiki link broken

https://github.com/SConsProject/scons/wiki/TestingMethodology Where's the link from? (What page) On Wed, Oct 11, 2017 at 8:33 PM, Daniel Moody wrote: > Seems this link is broken: > > https://github.com/SConsProject/scons/wiki/DeveloperGuide/ > TestingMethodology > > on the

[Scons-dev] EPEL SCons package

Greetings, I'm the SCons project Co-Manager. We're looking at simplifying our internal build and wondering if you use any of the RPM packaging logic in our repo's SConstruct, or if you work from the packages we upload to (currently) sourceforge or pypi? Thanks, Bill Deegan SCons Project Co

[Scons-dev] If you package SCons for a distribution (ubuntu, debian, macports, etc) please read

Greetings, Is anyone using the packages produced by running: python bootstrap.py? Or are you unpacking the .tar.gz for releases and using that? I'm looking to simplify bootstrap.py and if nobody uses the logic in there to build packages, then I'll drop it. (This would not affect SCons' ability

Re: [Scons-dev] epydoc on mac to produce PDF

; *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- > Rob Managan > > WCI/DP Division LLNL > > P.O. Box 808, L-095 > Livermore, CA 94551-0808 > Email: manag...@llnl.gov > > Phone: 925-423-0903 <(925)%20423-0903> FAX: 925-422-3389 > <(925)%20422-3389> >

[Scons-dev] epydoc on mac to produce PDF

Greetings, We use epydoc to produce the API docs for SCons. When I run bootstrap.py on my mac (MacOS Sierra), I get the following error in red below. I'm not a latex expert by any means. I'm wondering if anyone in our community has run into this issue and has a solution? Thanks, Bill

Re: [Scons-dev] D Lang config on ubuntu 16.04

This is on a personal system I'm configuring for work with scons. BTW. The buildbot worker running scons tests is ubuntu 14.04 LTS currently. On Thu, Sep 28, 2017 at 9:11 AM, Russel Winder wrote: > On Thu, 2017-09-28 at 17:06 +0100, Russel Winder wrote: > […] > > > >

[Scons-dev] D Lang config on ubuntu 16.04

Russel, I'm trying to configure a new system with gdc, dmd, and ldc, but alas I end up with: /usr/include/d/core/stdc/stdarg.d:48:5: error: undefined identifier __va_list_tag alias __va_list = __va_list_tag; A little googling suggests ldc + dmd = broken compiles and points to the d-apt

Re: [Scons-dev] [Scons-users] SCons repo recreated on github (yes this is the third one) PLEASE READ

Thomas, I think you're change may have broken some tests. Can you look at the failures in: http://buildbot.scons.org/#/builders/10/builds/3/steps/1/logs/stdio -Bill On Mon, Sep 25, 2017 at 12:30 PM, Bill Deegan <b...@baddogconsulting.com> wrote: > Thomas, > > Sorry looks like I

Re: [Scons-dev] [Scons-users] SCons repo recreated on github (yes this is the third one) PLEASE READ

first repo made it into > this last one though. As far as I can see, my pull request made it into the > first repo, but is not present in the new one? > > Cheers, > Thomas > > > On Sun, Sep 24, 2017 at 9:31 PM, Bill Deegan <b...@baddogconsulting.com> > wrote: > >&

Re: [Scons-dev] [Scons-users] SCons moves to GitHub! https://github.com/SConsProject/scons

Please recreate existing bitbucket pull requests on github. Thanks, Bill On Sun, Sep 24, 2017 at 4:19 PM, Tom Tanner <trtan...@btinternet.com> wrote: > On 18/09/2017 22:12, Bill Deegan wrote: > > Greetings, > > Well the day has finally come. > > SCons

[Scons-dev] SCons repo recreated on github (yes this is the third one) PLEASE READ

Greetings, Anatoly and Dirk pointed out that we could shrink the size of the repo, thus speeding up cloning and reducing disk footprint and cloning time. So I've reconverted, re-cherry-picked changes from the first git repo, deleted the second repo, created a third repo, pushed the update repo

Re: [Scons-dev] SCons moves to GitHub! https://github.com/SConsProject/scons

Also would I need to discard the current repo and create another to push this back to? On Sun, Sep 24, 2017 at 10:22 AM, Bill Deegan <b...@baddogconsulting.com> wrote: > I've not compressed a git repo before, do we lose any information? > > -Bill > > On Sun, Sep 24, 201

Re: [Scons-dev] SCons moves to GitHub! https://github.com/SConsProject/scons

I've not compressed a git repo before, do we lose any information? -Bill On Sun, Sep 24, 2017 at 7:54 AM, anatoly techtonik wrote: > I pushed my repository to https://github.com/techtonik/sconsize > and now git clone downloads only 9 Mb instead of 100 Mb, > > $ git

[Scons-dev] SCons on github reopened for business. PLEASE READ DETAILS

Greetings, So thanks to Anatoly for pointing out that the history was mangled by github's convertion from bitbucket to git. I've re-converted scons using hg-fast-export (https://github.com/frej/fast- export) and pushed to a NEW https://github.com/SConsProject/scons. *(If you have existing

[Scons-dev] Hold off on pull requests against git repo until further notice

Greetings, Looks like githubs hg->git repo dropped a bunch of history. I've done a conversion using hg-fast-export ( https://github.com/frej/fast-export) and pushed to https://github.com/SConsProject/test for community members to take a look and see if the history missing under the github

Re: [Scons-dev] SCons moves to GitHub! https://github.com/SConsProject/scons

, Sep 23, 2017 at 2:17 PM, Bill Deegan <b...@baddogconsulting.com> wrote: > let me try re-converting with hg-fast-import. > The internets say it does a better job. > > -Bill > > On Sat, Sep 23, 2017 at 2:13 PM, Bill Deegan <b...@baddogconsulting.com> > wrot

Re: [Scons-dev] SCons moves to GitHub! https://github.com/SConsProject/scons

let me try re-converting with hg-fast-import. The internets say it does a better job. -Bill On Sat, Sep 23, 2017 at 2:13 PM, Bill Deegan <b...@baddogconsulting.com> wrote: > Looks that way. This repo was converted earlier than the main one. > https://github.com/SConsProject/scon

Re: [Scons-dev] SCons moves to GitHub! https://github.com/SConsProject/scons

Looks that way. This repo was converted earlier than the main one. https://github.com/SConsProject/scons-gh-convert-git/commits/master/src/script/scons.py On Sat, Sep 23, 2017 at 2:11 PM, Bill Deegan <b...@baddogconsulting.com> wrote: > Must be the conversion from multiple hea

Re: [Scons-dev] SCons moves to GitHub! https://github.com/SConsProject/scons

t; > Blame doesn't show anything useful too. > > On Wed, Sep 20, 2017 at 1:34 PM, Jonathon Reinhart > <jonathon.reinh...@gmail.com> wrote: > > I am confident that this was the right move. I see this really lowering > the > > barrier to entry for people wishing to contri

[Scons-dev] Vote for SCons to be Sourceforge project of the month!

https://sourceforge.net/p/potm/discussion/vote/thread/22b0f0fd/ (Clunky voting system.. comment on their wiki to vote it seems..) ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev

[Scons-dev] scons-contrib migrated to github

New location: https://github.com/SConsProject/scons-contrib This is for code to share with the community. Currently it includes many user contributed builders. ___ Scons-dev mailing list Scons-dev@scons.org

Re: [Scons-dev] SCons moves to GitHub! https://github.com/SConsProject/scons

:) I've made handful of changes to the github wiki and scons.org. If you see any wiki pages referring to mercurial/bitbucket.org, please make an edit or send a note to the users mailing list where and what needs to be changed. Thanks, Bill On Mon, Sep 18, 2017 at 10:48 PM, Russel Winder

Re: [Scons-dev] SCons 3.0.0 release

..@lsst.org> wrote: > > > > This is fantastic news. Thank you very much to everyone for getting this > out. It’s been a huge amount of work. > > > > > >> On Sep 18, 2017, at 13:48 , Bill Deegan <b...@baddogconsulting.com> > wrote:

Re: [Scons-dev] SCons moves to GitHub! https://github.com/SConsProject/scons

Wiki has been migrated to github. On Mon, Sep 18, 2017 at 5:12 PM, Bill Deegan <b...@baddogconsulting.com> wrote: > Greetings, > > Well the day has finally come. > > SCons is moving to Github and git. > > Outstanding pull requests on bitbucket.org will need to be

[Scons-dev] SCons moves to GitHub! https://github.com/SConsProject/scons

Greetings, Well the day has finally come. SCons is moving to Github and git. Outstanding pull requests on bitbucket.org will need to be migrated to the new repo. The bugtracker is still at scons.tigris.org, but will be moved (real soon now) to github. Dirk has a start on a script to migrate

[Scons-dev] SCons 3.0.0 release

SCons - a software construction tool Release Notes This is SCons, a tool for building software (and other files). SCons is implemented in Python, and its "configuration files" are actually Python scripts, allowing you to use the full power of a

Re: [Scons-dev] Missing tools

cxx.py is in the manifest.in, so it should be in the package. On Mon, Sep 18, 2017 at 3:03 AM, Russel Winder wrote: > On Fri, 2017-09-15 at 15:44 +0100, Russel Winder wrote: > > Hi, > > > > I just did a "scons tar-gz" in my clone of the Mercurial repository, and > the > >

Re: [Scons-dev] Missing tools

They need to be added to Manifest.in I think. Good catch. -Bill On Fri, Sep 15, 2017 at 10:44 AM, Russel Winder wrote: > Hi, > > I just did a "scons tar-gz" in my clone of the Mercurial repository, and > the > clang.* and clangxx.* tools are not in the build even though

Re: [Scons-dev] [Scons-users] SCons 3.0, sconsign files and Py2 vs Py3.. how to handle sconsign imcompatabilities

's fine with me to wait. Should I open the PR > still on Bitbucket/hg then, or is there already a plan for the switch to > Github right after v3.0? > > Regards, > > Dirk > > > > Am 11. September 2017 14:59:48 MESZ schrieb Bill Deegan < > b...@baddogconsulting.com>

Re: [Scons-dev] SCons 3.0, sconsign files and Py2 vs Py3.. how to handle sconsign imcompatabilities

One thought would be to allow annotating the function with a specified csig. and/or version #. This would help (at least) for internal action functions (built in to scons). On Mon, Sep 11, 2017 at 10:23 AM, Tim Jenness <tjenn...@lsst.org> wrote: > > > On Sep 11, 2017, at 06:24,

Re: [Scons-dev] SCons 3.0, sconsign files and Py2 vs Py3.. how to handle sconsign imcompatabilities

Likely the rebuild py2 vs py3 is the action signature for functions now uses the bytecode. The bytecode is different between py2 and py3. Previously it was either pickling the function (which didn't adequately check for changes in the python functions), or dumping the string representation : For

Re: [Scons-dev] [Scons-users] SCons 3.0, sconsign files and Py2 vs Py3.. how to handle sconsign imcompatabilities

Dirk, I'd rather push that change to 3.1 (The need for speed release). That'll also give us time for some betas with those changes. -Bill On Mon, Sep 11, 2017 at 5:43 AM, Dirk Baechle <tshor...@gmx.de> wrote: > Hi Bill, > > Am 10. September 2017 04:13:37 MESZ schrieb Bi

Re: [Scons-dev] Sorry

No worries. I got it sorted with some help from Dirk. I guess I need to add scons packaging buildbot builder to catch such more quickly. -Bill On Mon, Sep 11, 2017 at 4:00 AM, Russel Winder wrote: > Bill, > > Apologies you had to construct DCommon.xml. Clearly I failed

Re: [Scons-dev] SCons distro package maintainers?

ere https://tracker.debian.org/p > kg/scons > > For Fedora see https://admin.fedoraproject.org/pkgdb/package/rpms/scons > / > > On Fri, 2017-09-08 at 14:00 -0400, Bill Deegan wrote: > > Any people who manage scons distro packages on the list? > >

[Scons-dev] SCons 3.0, sconsign files and Py2 vs Py3.. how to handle sconsign imcompatabilities

Greetings, This is (I hope) the last issue gating 3.0 release. *If we set the default pickle version to 2. (Currently set to HIGHEST_AVAILABLE, which means 4 for py3.5+ and 2 for py2.7)* If you run scons with py2.7 and then run again with py3.x, you'll get the following: ... scons: ***

[Scons-dev] SCons distro package maintainers?

Any people who manage scons distro packages on the list? -Bill SCons Project Co-Manager ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] **JUNK** Re: SCons, Mercurial, BitBucket, Git, and GitHub

Dirk, I guess I mis-understood. I thought there was a version for pushing to github already? -Bill On Thu, Aug 31, 2017 at 1:20 PM, Dirk Bächle wrote: > Hi all, > > On 31.08.2017 08:27, Dirk Bächle wrote: > > Bill, > > [...] > > > > True. This can also happen after the

Re: [Scons-dev] **JUNK** Re: SCons, Mercurial, BitBucket, Git, and GitHub

On Wed, Aug 30, 2017 at 9:55 AM, Gaurav Juvekar wrote: > Hi, > > > 4) Retaining a link to the tigris issue in the migrated issue to retain > > access to patches,etc. If possible a notation or perhaps a tag that > there > > are files on tigris, but if it's painful to do

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

Dirk, Indeed I see value in the following: 1) getting to github 2) integrated git+issues+wiki+ all the 3rd part integrations which work with github, but not with bitbucket 3) Migrating all the issues (frankly I'm not sure tigris will be around as long as github). There is useful information

Re: [Scons-dev] Problematic conflicts between C/C++ and D

On Wed, Aug 30, 2017 at 5:18 AM, Russel Winder <rus...@winder.org.uk> wrote: > On Tue, 2017-08-29 at 07:39 -0700, Bill Deegan wrote: > > env.get is just like a python dictionary. > > I can live with that. :-) > > > the order will depend on the order the tools are l

<    1   2   3   4   5   6   7   8   >