[RFC] Fixing early design flaws (package format, package version]

Request new features or present your ideas.
User avatar
illwieckz
Project Head
Posts: 438
Joined: Sat Aug 11, 2012 7:22 pm UTC
Location: France
Contact:

[RFC] Fixing early design flaws (package format, package version]

Postby illwieckz » Sat Mar 25, 2017 5:42 pm UTC

Last edited by illwieckz on Tue Mar 28, 2017 9:17 am UTC, edited 4 times in total.
This comment is licensed under cc ​​by 4 and antecedent.
User avatar
illwieckz
Project Head
Posts: 438
Joined: Sat Aug 11, 2012 7:22 pm UTC
Location: France
Contact:

Re: [RFC] Fixing early design flaws (package format, package version]

Postby illwieckz » Sat Mar 25, 2017 6:18 pm UTC

This comment is licensed under cc ​​by 4 and antecedent.
User avatar
Ishq
Project Head
Posts: 1138
Joined: Tue Mar 06, 2012 8:32 pm UTC

Re: [RFC] Fixing early design flaws (package format, package version]

Postby Ishq » Sat Mar 25, 2017 7:06 pm UTC

This seems acceptable to me.
User avatar
illwieckz
Project Head
Posts: 438
Joined: Sat Aug 11, 2012 7:22 pm UTC
Location: France
Contact:

Re: [RFC] Fixing early design flaws (package format, package version]

Postby illwieckz » Sun Mar 26, 2017 2:23 am UTC

This comment is licensed under cc ​​by 4 and antecedent.
User avatar
illwieckz
Project Head
Posts: 438
Joined: Sat Aug 11, 2012 7:22 pm UTC
Location: France
Contact:

Re: [RFC] Fixing early design flaws (package format, package version]

Postby illwieckz » Sun Mar 26, 2017 5:40 am UTC

This comment is licensed under cc ​​by 4 and antecedent.
User avatar
illwieckz
Project Head
Posts: 438
Joined: Sat Aug 11, 2012 7:22 pm UTC
Location: France
Contact:

Re: [RFC] Fixing early design flaws (package format, package version]

Postby illwieckz » Mon Mar 27, 2017 3:42 am UTC

.

It also fixes some bugs that were there because the engine was trying to handle two different behaviors for the same format, it's now far easier to handle two different behaviors for two different formats.

So we have now an unmerged complete chain with dpk/dpkdir support: map editor, map compiler, game engine, and all of them can load legacy pk3/pk3dir if some legacy stuff need it.

That was fast. :bugeyes:
This comment is licensed under cc ​​by 4 and antecedent.
User avatar
Viech
Project Head
Posts: 2137
Joined: Fri Aug 03, 2012 11:50 pm UTC
Location: Berlin

Re: [RFC] Fixing early design flaws (package format, package version]

Postby Viech » Wed Mar 29, 2017 10:14 pm UTC

I'm fine with changing the package extension to dpk. I agree that our packages are sufficiently different from pk3 to justify this change, given that the current same-name policy actually causes issues.

However, I'd like to maintain full debian version strings and debian version sorting. It's well documented, it's flexible, it's good and it works for us. Not to mention Darren would haunt us if we changed it. Don't invent a new version system for no other reason than personal taste. Debian standards are safe standards. (Take that from an Arch user. :wink:)

For the alpha/beta/release version flag issue, it is as simple as using r for the final release, that is a01 < … < a99 < b01 < … < b99 < r01 < r99. After that we would not even have to stop as debian versions should sort r99 < r100, but don't quote me on that. And to be fair, "Release 25" is more human-memorable than some 6.14 fractional number.

For 2017-03-24-1524 versus 20170324-1524 I do not feel strongly about it, though I can more easily read the former format and thus have decided on it when I "invented" these. It's fine that these strings are long because they are exclusively for in-development pk3s that are passed along internally, which should be verbose and easy to tell apart from any release pk3! I'd just stick to what we have, if only for consistency with older packages.
Responsible for: & , (map), (map texture editor), (material file generator), gameplay design & programming, artistic direction
User avatar
illwieckz
Project Head
Posts: 438
Joined: Sat Aug 11, 2012 7:22 pm UTC
Location: France
Contact:

Re: [RFC] Fixing early design flaws (package format, package version]

Postby illwieckz » Thu Mar 30, 2017 7:19 am UTC

This comment is licensed under cc ​​by 4 and antecedent.
User avatar
Viech
Project Head
Posts: 2137
Joined: Fri Aug 03, 2012 11:50 pm UTC
Location: Berlin

Re: [RFC] Fixing early design flaws (package format, package version]

Postby Viech » Thu Mar 30, 2017 11:41 pm UTC

Responsible for: & , (map), (map texture editor), (material file generator), gameplay design & programming, artistic direction
User avatar
illwieckz
Project Head
Posts: 438
Joined: Sat Aug 11, 2012 7:22 pm UTC
Location: France
Contact:

Re: [RFC] Fixing early design flaws (package format, package version]

Postby illwieckz » Fri Apr 07, 2017 3:15 am UTC

This comment is licensed under cc ​​by 4 and antecedent.

Return to “Ideas & Suggestions”

Who is online

Users browsing this forum: No registered users and 1 guest