Release process for 0.2.8_beta1

[Z-Man]

Short answer: because it would not work.

Long answers:
a) "make dist" requires a run of configure. You don't want bootstrap to run configure; it makes it impossible to configure build the project in an outside directory
b) "make dist" packs sources for distribution; some of the distributed files differ from those in CVS. For example, the version in the distributed configure.ac is hardcoded. Do the same modifications in place, and you'd be urged to commit the automatic canges to CVS.
c) "make dist", is a true make target; it has dependencies and reacts on modified input. You'd have to rebootstrap on every change you make.
d) "make dist" is standard behavior. You deviate from the standard only if you have a very good reason.

[Z-Man]

Status update: I'm in mail contact with swampy trying to get more info on the crash he gets.

It would be sweet if the others who downloaded the builds would give back a short report; I'll unhide the releases tomorrow or the day after that unless problems are reported, earlier if I get positive feedback.

[k]

The Windows build seems fine. I've only seen two problems.

1. Sometimes at the start of the match the camera is pointing straight down on top of the cycle. This seems to go away after setting CAMERA_SMART_GLANCE_CUSTOM 0 (personally I do not like the default behavior of the smart cam now when glancing).

2. If I start the dedicated server and the client on the same computer and I go the LAN browser I see two copies of the server.

[Luke-Jr]

1. Sometimes at the start of the match the camera is pointing straight down on top of the cycle.

I've seen that, but never more than once at a time... kinda assumed it was something I did

[Lucifer]

1. Sometimes at the start of the match the camera is pointing straight down on top of the cycle.

I've seen that, but never more than once at a time... kinda assumed it was something I did

YOu can make that happen by pressing glance keys before and during the countdown. It's actually a pretty cool effect, if you could figure out how to keep the effect without having it showing as a bug, that would be pretty cool.

[Lucifer]

Ack. I went to build the Mandriva packages (a day or two late, sorry), and got this:

Code: Select all

RPM build errors:
    File not found: /home/dave/rpm/tmp/armagetronad-0.2.8.0-0.6.beta1.1mdk-buildroot/usr/share/games/armagetronad/resource/included/HexaTRON/0.4.2.xml
    File not found: /home/dave/rpm/tmp/armagetronad-0.2.8.0-0.6.beta1.1mdk-buildroot/usr/share/games/armagetronad/resource/included/Your_mom/inaktek-.7.1.xml
    File not found: /home/dave/rpm/tmp/armagetronad-0.2.8.0-0.6.beta1.1mdk-buildroot/usr/share/games/armagetronad/resource/included/Your_mom/repeat-.3.1.xml
    File not found: /home/dave/rpm/tmp/armagetronad-0.2.8.0-0.6.beta1.1mdk-buildroot/usr/share/games/armagetronad/resource/included/n-gon/40.xml
    File not found: /home/dave/rpm/tmp/armagetronad-0.2.8.0-0.6.beta1.1mdk-buildroot/usr/share/games/armagetronad/resource/included/original/map-1.0.1.xml

Um, what names did the maps change to?

[Luke-Jr]

1. Sometimes at the start of the match the camera is pointing straight down on top of the cycle.

I've seen that, but never more than once at a time... kinda assumed it was something I did

YOu can make that happen by pressing glance keys before and during the countdown. It's actually a pretty cool effect, if you could figure out how to keep the effect without having it showing as a bug, that would be pretty cool.

Well, it gets stuck when it does happen...

Ack. I went to build the Mandriva packages (a day or two late, sorry), and got this:

Why aren't you just adding included recursively? :\

[Lucifer]

I've seen that, but never more than once at a time... kinda assumed it was something I did

YOu can make that happen by pressing glance keys before and during the countdown. It's actually a pretty cool effect, if you could figure out how to keep the effect without having it showing as a bug, that would be pretty cool.

Well, it gets stuck when it does happen...

Then I'm talking about something different. What happens for me when I do the deed with the glance keys is that the camera will point at the top of the cycle, then move up while watching the cycle shoot out. It's pretty cool.

Ack. I went to build the Mandriva packages (a day or two late, sorry), and got this:

Why aren't you just adding included recursively? :\

Because that's the Wrong Way to build a package. Files could get included that aren't supposed to be included. Also, by listing each file one by one, rpm's error checking is in full effect. If a file is copied to the build directory that isn't installed, I need to know why. Maybe it's a problem with the rpm, maybe it's a problem with the tarball.

[Luke-Jr]

Ack. I went to build the Mandriva packages (a day or two late, sorry), and got this:

Why aren't you just adding included recursively? :\

Because that's the Wrong Way to build a package.

Actually, the Right Way is to include everything copied during 'make install'. If there's a problem with the files, it's not RPM-specific, so it should be trapped w/ 'make install', not RPM-maker-prog.

Files could get included that aren't supposed to be included. Also, by listing each file one by one, rpm's error checking is in full effect. If a file is copied to the build directory that isn't installed, I need to know why. Maybe it's a problem with the rpm, maybe it's a problem with the tarball.

So why should RPM do error checking like this? It shouldn't, really, since any such problems are general to the game itself, not the RPM.

[Lucifer]

Why aren't you just adding included recursively? :\

Because that's the Wrong Way to build a package.

Actually, the Right Way is to include everything copied during 'make install'. If there's a problem with the files, it's not RPM-specific, so it should be trapped w/ 'make install', not RPM-maker-prog.

According to the documentation found here, you should list all files by hand, essentially.

Note that you should never use find to build a list of files to include but explicitely list all files (this'll show up bugs in new versions). The only exceptions is for locales for which you should use %find_lang %{name} in %install section and replace %files by %files -f %{name}.lang (see Appendix B).

And I"m not really interested in your opinion on the matter, I'm building a Mandriva package, and Mandriva's standards are the ones I will follow.

[Luke-Jr]

Because that's the Wrong Way to build a package.

Actually, the Right Way is to include everything copied during 'make install'. If there's a problem with the files, it's not RPM-specific, so it should be trapped w/ 'make install', not RPM-maker-prog.

According to the documentation found here, you should list all files by hand, essentially.

Then it's the standard way for building a Mandriva package-- not the right way (unless you can think of a reason why it should be done for a pkg and not for the entire install).

Note that you should never use find to build a list of files to include but explicitely list all files (this'll show up bugs in new versions). The only exceptions is for locales for which you should use %find_lang %{name} in %install section and replace %files by %files -f %{name}.lang (see Appendix B).

And I"m not really interested in your opinion on the matter, I'm building a Mandriva package, and Mandriva's standards are the ones I will follow.

Fine, but I don't see why filename changes are a problem when you're purposely requiring yourself to update a list when they do change.

[Lucifer]

And I"m not really interested in your opinion on the matter, I'm building a Mandriva package, and Mandriva's standards are the ones I will follow.

Fine, but I don't see why filename changes are a problem when you're purposely requiring yourself to update a list when they do change.

Then don't answer. I asked what happened to the files so I could fix the package, and you answered with "Don't build it that way!". That wasn't at all helpful, Luke, and it certainly didn't get the package built any quicker. If you want to be part of a team, you must be a team player. If I were asked right now to evaluate your performance as a team player, you would score an imaginary number. If you don't have an answer or a contribution, then don't say anything.

I was honored and excited to be invited to join the team. Now I can't look at the code without wondering what Luke will try to abuse me over, and I apparently can't build a package without Luke jumping all over my shit. There is a very dense collection of talent and competence gathered here, Luke, and yet you insist on assuming incompetence and behaving like you're somehow "better" than anyone else here.

I'm not going to deliver an ultimatum, but I'm also not going to put up with this shit any longer. I have better things to do with my time than argue with Luke.

[Luke-Jr]

and you answered with "Don't build it that way!".

Actually, I asked WHY you were building that way... You could have answered "that's how Mandriva wants people to do it"

[Lucifer]

and you answered with "Don't build it that way!".

Actually, I asked WHY you were building that way... You could have answered "that's how Mandriva wants people to do it"

You knew the answer to my question, why didn't you provide that in your response?

[Luke-Jr]

and you answered with "Don't build it that way!".

Actually, I asked WHY you were building that way... You could have answered "that's how Mandriva wants people to do it"

You knew the answer to my question, why didn't you provide that in your response?

Actually, I had no idea Mandriva did it anything like that, let alone suggested it to others.