Log for #openttdcoop.devzone on 9th November 2011:
Times are UTC Toggle Colours
00:34:49  *** Zuu has quit IRC
01:31:52  *** frosch123 has quit IRC
06:37:59  *** JVassie has joined #openttdcoop.devzone
06:59:58  *** JVassie has quit IRC
07:50:10  *** andythenorth has joined #openttdcoop.devzone
08:02:39  *** ODM has joined #openttdcoop.devzone
08:10:22  <Brot6> FIRS Industry Replacement Set - Feature #3223 (New): industry availability callback (planetmaker) @
09:28:09  *** andythenorth has quit IRC
09:30:07  *** andythenorth has joined #openttdcoop.devzone
10:13:11  <Brot6> NewGRF Meta Language - Feature #3224 (New): Support for NewGRF v8 (planetmaker) @
10:14:45  <Yexo> planetmaker: is opengfx really a problem?
10:15:00  <Yexo> grfv8 will only come after 0.2 is released, so as long as opengfx can use 0.2 there shouldn't be a problem
10:15:34  <planetmaker> Yes that then shouldn't be a problem
10:15:58  <planetmaker> The point about OpenGFX is, that it should at least support current stable and last stable branch
10:16:02  <planetmaker> (and nightlies of course)
10:16:34  <Yexo> the good point is that it's unlikely for opengfx to require newer nml versions, you could easily keep using 0.2 for a long time
10:16:42  <planetmaker> currently is supports all versions of OpenTTD which have base sets, but ...^
10:17:05  <planetmaker> though it will need newer versions. Like action5 and so on
10:17:16  <Yexo> 0.2.1, 0.2.2 :p
10:17:23  <planetmaker> yes, no problem, feasible
10:17:33  <planetmaker> we just declare 0.2.x long-term stable :-)
10:17:52  *** andythenorth_ has joined #openttdcoop.devzone
10:17:52  *** andythenorth is now known as Guest16382
10:17:52  *** andythenorth_ is now known as andythenorth
10:18:45  *** Guest16382 has quit IRC
10:46:41  *** SmatZ has quit IRC
10:46:42  *** KenjiE20 has quit IRC
10:46:42  *** michi_cc has quit IRC
10:46:42  *** XeryusTC has quit IRC
10:46:42  *** Terkhen has quit IRC
10:46:42  *** seberoth has quit IRC
10:49:07  *** seberoth has joined #openttdcoop.devzone
10:49:57  *** SmatZ has joined #openttdcoop.devzone
10:50:23  *** michi_cc has joined #openttdcoop.devzone
10:50:27  *** Terkhen has joined #openttdcoop.devzone
10:50:27  *** XeryusTC has joined #openttdcoop.devzone
11:48:16  *** frosch123 has joined #openttdcoop.devzone
12:06:39  <frosch123> 10:15:58  <planetmaker> The point about OpenGFX is, that it should at least support current stable and last stable branch <- current opengfx does not work in 1.1 anyway, does it?
12:06:59  <planetmaker> of course it does
12:07:12  <frosch123> or it does not work in < 1.1 ?
12:07:13  <Yexo> even with the gridliens?
12:07:13  <planetmaker> it should even work in 0.7
12:07:20  <frosch123> no, we discussed that
12:07:23  <planetmaker> the gridlines should also work
12:07:30  <frosch123> we need a changed installer for the next version
12:07:32  <planetmaker> I implement that as conditional actionA
12:07:38  <frosch123> due to rivers maybe?
12:07:47  <planetmaker> that needs it neither
12:07:49  *** KenjiE20 has joined #openttdcoop.devzone
12:08:15  <planetmaker> they use different spritesets for different versions
12:08:23  <planetmaker> and different action0 as well
12:08:27  <frosch123> something caused glitches
12:08:36  <planetmaker> can you show me?
12:08:49  <planetmaker> I thought I sorted river glitches with all versions
12:08:51  <frosch123> i think it was the river action 0 flag for different sprite order
12:08:55  <planetmaker> yes
12:09:03  <planetmaker> That's solved. By means of action7
12:09:10  <frosch123> ok, did not know that
12:09:40  <planetmaker> indeed I missed that part initially :-)
12:09:54  <planetmaker> but it's not a principle problem
12:15:27  *** hanf has joined #openttdcoop.devzone
12:23:37  *** ChillCore has joined #openttdcoop.devzone
12:25:21  <ChillCore> planetmaker Ammler: I have been searching but I did not find the way how to push the mq alone instead of the entire repo,
12:25:41  <ChillCore> must it be applied or not and what is the command to enter
12:25:56  <ChillCore> Also hello everyone ;)
12:25:58  <planetmaker> you need to create a(nother) repo in the respective patch queue dir
12:26:03  <planetmaker> yes, and hello :-)
12:26:13  <frosch123> if you go into ".hg/patches" you will find a hg repo
12:26:13  <planetmaker> i.e. in .hg/patches
12:26:25  <planetmaker> you run hg init
12:26:41  <frosch123> if using a reasonable up-to-date hg, i think it is even the default to make it a repository
12:26:53  <ChillCore> I have that already by exporting the applied patch to the mq
12:26:58  <planetmaker> I never noticed
12:27:30  <planetmaker> ChillCore: then you don't operate on the main repo (openttd) but on the mq repo (.hg/patches)
12:27:42  <planetmaker> thus you need to setup that repo with the default-push etc
12:27:52  <planetmaker> and call the push command from / for that
12:28:08  <ChillCore> I am using the nautilus gui extension by the way, but do not mind going to the terminal
12:28:57  <planetmaker> I've no ideas about GUI extensions :-P
12:29:36  <ChillCore> Me neither apparantly :P
12:30:05  <planetmaker> for a GUI it probably is like a separate repo / project
12:30:20  <planetmaker> except if it explicitly supports versioned mqs
12:31:12  <ChillCore> I may have to enable that still; I remember reading something about that.
12:31:48  <ChillCore> I will do some more searching in that direction then.
12:32:24  <ChillCore> Thank you. I'll be back in a bit.
12:32:31  <planetmaker> so you want rather use a mq (to better keep the patches), right?
12:32:42  <planetmaker> I guess I would, too :-)
12:33:13  <ChillCore> I cannot push the entire repo unless the file limit is increased even more
12:33:56  <planetmaker> 100MB is not enough?
12:34:00  <ChillCore> see the (now removed) file in my repo ... commit 1
12:34:02  <ChillCore> no
12:34:11  <ChillCore> unfurtunately
12:34:21  <planetmaker> not even piecewise as Ammler suggested?
12:34:42  <ChillCore> I have not yet tried to be honest
12:35:40  <ChillCore> I had the idea that when creating a repo you put the clean HG repo already in place, I clone it and then only need to push my changes
12:37:11  <ChillCore> I can try to push in pieces but Ammler suggested that it made more sense to only push the MQ, which I kind of agree with
12:37:35  <ChillCore> sorry for the highlights Ammler
12:38:16  <ChillCore> Although I do not really understand how peple than pull the repo for compiling themselves
12:38:18  <planetmaker> Yes, that kinda makes sense
12:38:37  <planetmaker> though it kinda also requires to keep updating patches as the underlying repo changes
12:38:48  <ChillCore> peple / people
12:39:22  <planetmaker> though... locally it might not change. And for the CF we probably could find a solution, too
12:39:34  <ChillCore> If space is not an issue maybe it would be better to push the entire repo anyway?
12:39:55  <Yexo> if you push the entire repo you're basically back to one single big diff
12:40:12  <Yexo> the advantage of pushing the mq stack is that you push the individual patches
12:40:18  <ChillCore> planetmaker: The previously highlighted person said something like that is already there
12:40:23  <Yexo> which should make it easier to update (since you update each patch separately)
12:40:57  <planetmaker> ChillCore: the highlight for Ammler on this topic might be good :-P
12:41:46  <planetmaker> it'd make it especially easy to change the patch queue (remove / add) single patches
12:42:15  <ChillCore> Yexo: Yes that is the idea for now as splitting a +2MB patch is too much work for a patchpack that is about to die, when restarting my patchpack I would use seperate mq for each patch.
12:42:43  <Yexo> a mq is a patch queue, so you'd just need one mq for all patches
12:43:13  <planetmaker> a mq works like "first apply patch A". Then apply ontop patch B. Then ontop patch C etc
12:43:16  <Yexo> so for now you want to keep using your current big patch?
12:43:18  <planetmaker> one depending on the other
12:43:37  <ChillCore> I would like to restart on current trunk for obvious reasons and bumping it as is would be an insane task, with recent changes to trunk.
12:44:12  <planetmaker> then making kinda a new PP with means of a patch queue is probably the solution you want
12:44:18  <Yexo> I'd say if you restart, do it properly by using mq (or similar like using git and rebase)
12:44:52  <ChillCore> Yexo: yes MQ with 1 patch for now. and doing it properly afterwards
12:45:00  <planetmaker> And then start with one patch. Make it work. Then add the next patch to the queue
12:45:16  <planetmaker> oh, you want this one big patch as patch in the mq?
12:45:38  <planetmaker> well, sure. Also feasible
12:45:52  <ChillCore> planetmaker: As Ammler suggested ...
12:47:16  <planetmaker> I'm not entirely sure he suggested that. But yes, feasible
12:47:47  <ChillCore> I can show the PM if you want :)
12:47:49  <planetmaker> Though if you start on v14 (or however you name them), it might make sense to just take the original single patches and make a completely new mq from it
12:47:53  <Yexo> ChillCore: what's the point of using MQ with 1 patch?
12:47:59  <planetmaker> is it another which I didn't get, ChillCore?
12:48:38  <Yexo> ie what is the big patch you want to use for that?
12:48:45  <ChillCore> Yeah ... not all converstaion was forwarded betwwne the three of us.
12:49:19  <ChillCore> Yexo: the last posted patch in my thread, and continue on that for a little while longer
12:49:50  <Yexo> if you continue of that single patch you might as well skip MQ and just push the repo
12:51:47  <ChillCore> true, but if I do it now I could pop the complete patch and continue making sepperate ones afterwards more easily? without the need for a second repo?
12:51:52  <ChillCore> I am new to this
12:51:59  <planetmaker> yes, you could
12:52:15  <planetmaker> your deduction is correct
12:52:36  <ChillCore> Credits to Ammler.
12:53:15  <Terkhen> ChillCore: I managed my (now ancient) patch pack as a collection of different patches, see
12:53:16  <Webster> Title: / - tppp - Terkhens Personal Patch Pack: A custom build for OpenTTD - Google Project Hosting (at
12:53:18  <Yexo> I still think you're wasting your time continuing with the current patch if you're going to start over anyway
12:53:27  <Terkhen> I did not know about mq back then, but it would have made things way more easy
12:54:55  <Terkhen> I had no qualms at all about savegame compatibility between different versions, though
12:55:48  <ChillCore> Terkhen: I know and I see how it is better. My problem was is that I did not know how to pull complete diffs instead of many smaller ones to be able to debug more easily
12:56:24  <ChillCore> I will hande savegamecompatibility as a seperate patch (when restarting)
12:56:36  <ChillCore> hande /handle
12:56:37  <planetmaker> that's sensible
12:56:45  <Yexo> ChillCore: might I ask your reasons for not restarting right now?
12:56:48  <Terkhen> yes, I wondered about doing that too
12:56:55  <Terkhen> a patch for keeping savegame compatibility
12:57:24  <ChillCore> Yexo: many patches need adaption to trunk and I am waiting for Linux Mint 12 to be realeased
12:57:26  <Terkhen> then I realized that I never updated my openttd version in the same game and forgot about compatibility :P
12:58:10  <ChillCore> I have bought a 1 terra HDD just for OpenTTD and will dedicate an AMD64 +3400 just for that
12:59:58  <ChillCore> Terkhen: :P I had that too many times before ... Doing the patchpack thought me a lot on the matter. Too bad I screwed up trunk compatibility when I started experimenting.
13:02:53  <ChillCore> Yexo: My current version will not see many big patch inclusions anymore, just some bugfixes as gratitude for the people that have been playing for a long time and would like to finish their games
13:03:11  <ChillCore> Maybe just the new infra maintenance patch
13:03:19  <Yexo> fair enough :)
13:04:13  <ChillCore> Anyway ... going to read some more to put the MQ under version control
13:04:35  <ChillCore> I'll be back as I am sure I will have more questions soon
13:05:28  <ChillCore> And I have a visitor now
13:05:42  <planetmaker> enjoy
13:06:09  <ChillCore> Thank you again, all. planetmaker: I will.
13:08:16  <ChillCore> How do  I log out? Or do I just close the window ... Oh boy and to think I write a patchpack :P
13:08:55  <Yexo> irc? just close the window
13:09:23  <ChillCore> Okidoki, laters ...
13:09:25  <V453000> bye :p
13:10:01  <ChillCore> bye ;)
13:10:12  *** ChillCore has quit IRC
14:58:40  *** andythenorth has quit IRC
15:54:44  <Ammler> hmm, I didn't suggest to make just one patch
15:54:57  <Ammler> I just said, he can also submit his current patch as mq
15:56:28  <planetmaker> yes, that's what we understood
15:56:39  <planetmaker> we just wondered why he wants that at all
15:57:20  <Ammler> well, why did he like to push the openttd repo?
17:09:24  <Brot6> grfcodec: update from r839 to r841 done -
17:22:53  *** andythenorth has joined #openttdcoop.devzone
17:23:00  <planetmaker> Ammler: he only did that as I didn't recall that way
17:25:01  *** Zuu has joined #openttdcoop.devzone
17:32:52  <Brot6> vactrainset: compile of r1 still failed (#3044) -
17:39:02  <Brot6> Following repos rebuilds successful without any difference to earlier nightlies builds: bros (1 warnings), transrapidtrackset, 2cctrainset (6 warnings), worldairlinersset, heqs, basecosts, nutracks, water-features, 32bpp-extra (2 warnings), newgrf_makefile, snowlinemod, metrotrackset (Diffsize: 1), fish (41 warnings), ttrs (7 warnings) (Diffsize: 1324), ogfx-trees, smts (Diffsize: 8), chips (1 warnings), comic-houses (3 warnings)
17:39:03  <Brot6> (Diffsize: 22)
19:02:32  <Brot6> clientpatches: compile of r23177 still failed (#2964) -
19:04:31  <Brot6> serverpatches: compile of r23177 still failed (#2966) -
19:06:26  <Brot6> 32bpp-ez-patches: compile of r23177 still failed (#2446) -
19:11:04  *** JVassie has joined #openttdcoop.devzone
19:44:57  *** andythenorth is now known as Guest16500
19:44:58  *** andythenorth has joined #openttdcoop.devzone
19:45:35  *** Guest16500 has quit IRC
21:40:58  *** frosch123 has quit IRC
22:07:57  *** andythenorth has quit IRC
22:53:03  <Brot6> NewGRF Viewer - Revision 24:bdafd40d5cd1: First stab at unicode strings. (UnicycleBloke) @
22:53:03  <Brot6> NewGRF Viewer - Revision 25:6072eb175f4f: Update 'NFO' display after each edit. (UnicycleBloke) @
22:53:03  <Brot6> NewGRF Viewer - Revision 26:9cf288e32231: Minor updates to string editing - always accept \< and \n (UnicycleBloke) @
23:15:24  *** Zuu has quit IRC
23:24:12  *** ODM has quit IRC

Powered by YARRSTE version: svn-trunk