Hi Ben, Hi All,
I'm quite conservative when it comes to relying on others'
infrastructure so I need some help making me take the plunge. Please see
below:
On Thu, Dec 17, 2015 at 7:15 AM, Ben Coman <btc(a)openinworld.com> wrote:
>
> > On Wed, Dec 16, 2015 at 1:00 AM, Ben Coman <btc(a)openinworld.com> wrote:
> >>
> >>
> >> On Wed, Dec 16, 2015 at 10:43 AM, Ryan Macnak <rmacnak(a)gmail.com>
> wrote:
> >> >
> >> > What would be more helpful is if the VM build was fixed to work with
> a cross compiler, so it would compile fast enough to test ARM and MIPS on
> Travis CI alongside IA32 and X64.
> >> >
> >> > It would also help if the top-of-tree Intel VMs were always kept
> working so we'd know which change broke something. Moving the Subversion
> repository to a more reliable host (which likely means migrating to Git)
> would also cut down on the false positives Travis reports because the
> Subversion server has a habit of dropping connections.
> >>
> >> +1 github :)
>
> btw, Did you know that github supports subversion clients since 2011 [1]?
> Here are supported features [2]. Are these sufficient for your
> current svn workflows?
> Potentially we could have ONE repository and those liking subversion
> can stick with it and those liking git can use that. Of course, this
> would need to be proven.
>
Ah, that's interesting. So my concern is whether github is a safe
long-term bet. Specifically what is there to prevent some third party from
buying github, or of github going public and the board taking the decision,
or github on its own, deciding to charge for hosting, keeping the data
hostage to extract payment? What safeguards are in place to prevent this?
I'm not interested in "this will never happen" arguments. I'm interested
in hard data please.
[4] Provides pragmatic advice for cutting over. Esteban appears to
> have done similar to step 1 and 2 [3] - but it seem sometimes his
> modifications directly update this mirror so its not clear to see when
> that branch is an *exact* copy of the current svn trunk. So I'd love
> to see a github repository that is always an *exact* mirror of the svn
> repository, with any pharo mods occurring in a branch off that. Even
> better if the repository for svn users resides on github in place of
> that mirror.
>
> I've been googling around for problems reported using github via an
> svn client, and haven't found any smoking guns.
> Is this something we can trial? I'm willing to put some effort into
> it. A key requirement would be not interrupting Eliots work on
> Spur-64. Potentially we could stay for months on step 3 [4] with the
> CI infrastructure running on the git side, but code check-ins
> continuing onthe svn side.
>
> btw2, [5] provides a use case for the advantages of a full switch.
>
> cheers -ben
>
> [1] https://github.com/blog/966-improved-subversion-client-support
> [2] https://help.github.com/articles/support-for-subversion-clients/
> [3] https://github.com/pharo-project/pharo-vm/network
> [4]
> http://blogs.atlassian.com/2013/01/atlassian-svn-to-git-migration-technical…
> [5]
> http://blogs.atlassian.com/2013/01/svn-to-git-how-atlassian-made-the-switch…
>
--
_,,,^..^,,,_
best, Eliot
Hi,
Has anybody made a dark theme for Squeak with dark window background etc.
My eyes are becoming much more sensitive to the bright white background, so
a dark theme would be nice to switch to :-)
Best,
Karl
Chris Muller uploaded a new version of Collections to project The Trunk:
http://source.squeak.org/trunk/Collections-cmm.675.mcz
==================== Summary ====================
Name: Collections-cmm.675
Author: cmm
Time: 3 January 2016, 3:33:44.302 pm
UUID: d019e6cc-abbb-4077-9e3d-2f471f6fb07a
Ancestors: Collections-eem.672
grownBy: should answer the same class of object asked to be grown.
=============== Diff against Collections-eem.672 ===============
Item was changed:
----- Method: SequenceableCollection>>grownBy: (in category 'copying') -----
+ grownBy: length
- grownBy: length
"Answer a copy of receiver collection with size grown by length"
+ ^ (self class ofSize: self size + length)
+ replaceFrom: 1 to: self size with: self startingAt: 1 ;
+ yourself!
-
- | newCollection |
- newCollection := self species ofSize: self size + length.
- newCollection replaceFrom: 1 to: self size with: self startingAt: 1.
- ^ newCollection!
Happy New Year Everyone,
We are excited to announce that Squeak is now officially supported on
Travis-CI <http://travis-ci.org/>.
This means you can finally set "language: smalltalk" in your *.travis.yml*
in
order to run tests for your GitHub-hosted Squeak/Smalltalk projects on
Travis-CI.
Builds will start in less than 10 seconds, because they run on Travis' new
container-based infrastructure. The new build process comes with some great
features such as faster build times, Linux and OS X support, and more [1].
We are currently discussing how to configure Smalltalk builds in the future
(see [2]),
but in the meantime, [3] should get you started.
If you have any bug reports or feature requests, please file an issue at
[4].
Also, feel free to contribute to the smalltalkCI framework that we are
maintaining
and that Travis uses to build your Smalltalk projects.
Happy testing!
Steffen, Jonas, Lennard, Christopher and Fabio (HPI students)
[1] https://github.com/hpi-swa/smalltalkCI#features
[2] https://github.com/hpi-swa/smalltalkCI/issues/20
[3] https://github.com/hpi-swa/smalltalkCI#how-to-use
[4] https://github.com/hpi-swa/smalltalkCI/issues
Hi Chris,
what about using the idea of HashedCollection >> #growSize? It is "self
class goodPrimeAtLeast: array size * 3 // 2 + 2". Is it specific to hashing
that a prime number is used there?
Best,
Marcel
--
View this message in context: http://forum.world.st/The-Inbox-Collections-cmm-673-mcz-tp4868946p4868959.h…
Sent from the Squeak - Dev mailing list archive at Nabble.com.