[jamming] Majam - keeping jam up-to-date

[Groleo Marius]

On 7/31/06, Kai Backman <kaib at google.com> wrote:
> Hi,
>
> First I must confess that I've been planning a similar integration for a while
> so I'm strongly biased towards more development activity .. :-)
>
>   There are already several "new" jams (ftjam, boost jam, kjam etc) around that
> haven't replaced the current Perforce codeline. These are the details I think
> are important in case you want a new version widely used:
>
> - It must be faster or as fast as jam 2.5. You should measure speed using an
> automated test to make it convincing.
>
> - It needs to retain the portable C implementation and the minimalist approach
> to including new constructs in the language or implementation.
>
> - Currently Jam is about 15kLOC, you probably want to keep it from growing
> too much, or even try to prune it back slightly.
>
> - A solid regression, unit test set would be beneficial.
>
Yes, a good test collection would convince even more.
As tests, I added deptest, and other 3 basic tests.

- I would add a better documentation and some examples.
- Something that I think would prove useful, would be an automake facility.
- Maybe porting to Win9x/ME too.

> Here is a list of resources I've allocated. In case we can agree on the vision,
> we should pool effort:
>
> Subversion repository and issue tracker (Google Code hosting):
> http://jamredux.googlecode.com/svn/trunk
> http://code.google.com/p/jamredux/
>
> Webspace and domain on VPS server (nothing on the server yet):
> www.jamredux.org
>
> I picked jamredux (jamr) as a pun on the original make redux.. ;-)
>
> On 7/31/06, Craig Allsop <cjamallsop at gmail.com> wrote:
> > Why wouldn't one use perforce's public depot for this job - this is where
> > most of the existing patches have been placed?
>
> I think I'm siding with Groleo in using Subversion instead of P4. Because of
> svn's copy-modify-merge style of work it is more suited for clients not having
> a stable network connection to the repository. My personal experience,
> having worked with both P4 and SVN in a distributed team, was that SVN had
> less downtime due to network issues.
>
> That said, the P4 depot many interesting patches, like:
> http://maillist.perforce.com/pipermail/jamming/2002-January/001527.html
>
> Alen also has a ton of local modification, which I'm sure he is happy to share
> or I can send them over in case it's OK with him. I have also some minor
> changes in the repository above.
>
> @Groleo: I checked out your SF repos and noticed you don't follow the
> canonical trunk/tags/branches setup? How are you planning on doing
> release branches and tagging?
>

ATM, I havent thought at that. I'm concentrating on gathering/setting things up,
though it shouldn't be hard to do a svn copy ;)

> Take care,
>
> Kai
>
> --
> Kai Backman, Software Engineer, kaib at google.com
>


-- 
Regards, Groleo!