Mark Wedel | 1 Dec 2008 08:30
Favicon

Re: Client Snapshot Builds


  Quick notes (I've probably missed some - if I've missed anything important, 
follow up).

The list of supported platform is largely based on user input.  I've not had a 
mac, so that is based on someone providing patches (if necessary) and saying it 
works.  On going testing of those platforms does not happen by me, and maybe not 
at all.  At one point, I think the list was a lot longer, but then we started 
asking 'just when is the last time someone tried to compile on irix?'.

  For what its worth, I've moved for redhat linux to solaris (x86/amd64) so 
cover that base.

  The official release cycle is slow for a variety of reasons - off the top of 
my head:

- Broken release system - the tools/components are there, but changes have been 
made (addition/removal of file being most common) such that release/packaging 
fails.  Not hard to fix, but takes time.
- For official releases, desire to have stable components (no big check in the 
day before).  But folks also like to have a chance to fix bug and make other 
changes before the release, which sort of goes against stability (fixing bugs 
should make things more stable, but not always the case)
- Scheduling becomes a problem - between the packaging, uploading, and updating 
the page on sourceforge, it would be a couple hour process.  It may be the case 
that I have the time right now, but to let everyone have a chance to put in the 
patches, change, etc it means a couple weeks time, when I may not have time.
- The only real part of the official release was the source tar balls.  Binaries 
may come later or not at all (I only did x86_64 rpms - never did anything more)

(Continue reading)

Rick Tanner | 2 Dec 2008 08:41
Favicon

Re: (Automated) Client Snapshot Releases


Kevin R. Bulgrien wrote:
> 
> What might it take to break the blockade on 2.x client releases?  

I would say squashing the double character issue that you mentioned
later on in your email.

> P.S. Right now my build system is x86_64, and unfortunately x86_64 RPMs
> seems to have the "[ 1876788 ] Doubled characters in GTK clients" bug.

Or move what is currently in trunk right now and make it 1.12.0 or
something similar.

Kevin R. Bulgrien | 2 Dec 2008 13:48
Picon

Re: (Automated) Client Snapshot Releases

> > What might it take to break the blockade on 2.x client releases?
>
> I would say squashing the double character issue that you mentioned
> later on in your email.
>
> > P.S. Right now my build system is x86_64, and unfortunately x86_64 RPMs
> > seems to have the "[ 1876788 ] Doubled characters in GTK clients" bug.
>
> Or move what is currently in trunk right now and make it 1.12.0 or
> something similar.

It might seem fair to say dealing with that bug is required, but I am
pretty sure that information you dug up says it is a bug on the released
branch which pretty much freezes a "stable" branch too.

( https://bugs.launchpad.net/ubuntu/+source/crossfire-client/+bug/87194 )

Of course, it is ideal to fix that, but 32-bit players should still be
able to use the client, but I do not have the level of GTK experience
at this point to know this is going to be something I can fix.

That said, I'm in the process of setting up a 32-bit build environment
to check, but so far I can only reproduce the problem when building with
rpmbuild to make RPMs, and people aren't providing the level of detail
about how they build to help with the debug/reproduction.  It does not
happen when building "normally" with ./configure; make; make install,
and, I've even tried the same ./configure parameters the crossfire.spec
file uses.  Probably next up is to diff the spew from a regular build
with an rpmbuild.

(Continue reading)

Rick Tanner | 2 Dec 2008 18:01
Favicon

Re: (Automated) Client Snapshot Releases


Kevin R. Bulgrien wrote:
> 
> In summary, I do not think the double text issue should hold back a
> working snapshot.

The double characters in the GTKv-2 client on a 64bit system makes the
client unusable, IME.

Kevin R. Bulgrien | 3 Dec 2008 00:02
Picon

Re: (Automated) Client Snapshot Releases

> > In summary, I do not think the double text issue should hold back a
> > working snapshot.
>
> The double characters in the GTKv-2 client on a 64bit system makes the
> client unusable, IME.

A working 32-bit RPM, a working 64-bit tarball, etc. is not the same as
a non-working 64-bit RPM...  'Nough said.
Kevin R. Bulgrien | 4 Dec 2008 06:42
Picon

[ 1876788 ] Doubled characters in GTK clients (trunk GTK-V2 fixed)

The trunk GTK-V2 client is considered fixed as of SVN 10827.  This
client is compatible with branch servers (metalforge).

Some additional attempt will be made to verify/reproduce/fix problem
in the GTK-V1 client.  Branch client code is quite different from trunk,
but it should be quite simple to backport changes there as needed.

The issue is not closed yet because the trunk GTK-V1 client and both
branch clients have not been examined or worked on yet.

Kevin Bulgrien

P.S. Credit is due mwedel for facilitating this fix.
Nicolas Weeger | 6 Dec 2008 12:04
Favicon

Re: [ 1876788 ] Doubled characters in GTK clients (trunk GTK-V2 fixed)

Le jeudi 04 décembre 2008, Kevin R. Bulgrien a écrit :
> The trunk GTK-V2 client is considered fixed as of SVN 10827.  This
> client is compatible with branch servers (metalforge).
>
> Some additional attempt will be made to verify/reproduce/fix problem
> in the GTK-V1 client.  Branch client code is quite different from trunk,
> but it should be quite simple to backport changes there as needed.
>
> The issue is not closed yet because the trunk GTK-V1 client and both
> branch clients have not been examined or worked on yet.

Nice, thanks for the fix!

Nicolas
--

-- 
http://nicolas.weeger.org [Petit site d'images, de textes, de code, bref de 
l'aléatoire !]
_______________________________________________
crossfire mailing list
crossfire@...
http://mailman.metalforge.org/mailman/listinfo/crossfire
Nicolas Weeger | 6 Dec 2008 12:15
Favicon

Re: C++/Qt server version

Hello.

Reminder, the page http://wiki.metalforge.net/doku.php/dev%3Aserver_design and 
specifically the 'player-wise' section is waiting for you and your ideas! :)

Nicolas
--

-- 
http://nicolas.weeger.org [Petit site d'images, de textes, de code, bref de 
l'aléatoire !]
_______________________________________________
crossfire mailing list
crossfire@...
http://mailman.metalforge.org/mailman/listinfo/crossfire
Marc Lehmann | 12 Dec 2008 22:55
Picon
Favicon

Re: Seeking life...

On Sat, Nov 01, 2008 at 01:32:22PM +0100, Nicolas Weeger
<nicolas.weeger@...> wrote:
> So, anyone working on something? Anyone having plans for working on CF? Or can
> we close the shop down?

I know, it's a bit late for a reply, but I found it rather satisfying and
funny.

The crossfire/metalforge folks are *actively* driving away everybody who
is willing to do work, and you still seem to wonder about it. Now that's
weird.

Contrast this to Deliantra.

Content:

- deliantra has had vastly improved 64x64 graphics with *working* smoothing
  for over a year.
- almost all textures have been redone, many items and buildings are now
  actually 3d models. known proprietary material has been removed.
- a myriad of map bugs have been fixed.
- npc dialogs have been vastly improved in the server, and most content
  has been updated, starting from mere rewriting of many of the existing (but
  wrong) texts in maps to adding completely new quests, cities and even
  whole new contintents!
- many areas have been bigworldised (this is technically very easy in deliantra).
- there is a multi-stage tutorial and many areas of the world (including
  scorn) have been redone almost completely to work more logically and
  give beginners a more logical introduction to the game. of course,
  the server can give (optional) hints
(Continue reading)

Lalo Martins | 13 Dec 2008 00:07
Picon
Gravatar

Re: Seeking life...

quoth Marc Lehmann as of Fri, 12 Dec 2008 22:55:54 +0100:
> On Sat, Nov 01, 2008 at 01:32:22PM +0100, Nicolas Weeger
> <nicolas.weeger@...> wrote:
>> So, anyone working on something? Anyone having plans for working on CF?
>> Or can we close the shop down?
> 
> I know, it's a bit late for a reply, but I found it rather satisfying
> and funny.

No, it's just late, really.  After 1.5 months of a lot of activity 
happening, your reply just came of whiny and clueless.  Or did you 
completely miss the server rewrite thread, the news about having code and 
content leaders, the discussions about Tallworld?  Ah, you probably did.  
Ok then.

> The crossfire/metalforge folks are *actively* driving away everybody who
> is willing to do work, and you still seem to wonder about it. Now that's
> weird.

Whatever helps you sleep at night, dude.

> Contrast this to Deliantra.

You got some stuff working?  Good for you.  Ranting and flaming about it 
won't get you anywhere, though, except for losing any scraps of respect 
some people (me included) still had for you and your project.

Please don't post to this list anymore.

best,
(Continue reading)


Gmane