Oolite Bulletins

The way Linux software packaging seems to handle this is to have a "Provides" concept.
So you could have:
oxp.author.shipset.addition (provides oxp.author.shipset)
oxp.author.shipset.replace (provides oxp.author.shipset)
oxp.author.extraships (depends on oxp.author.shipset)

This wouldn't be that difficult to code in, I think. The question is "if you install the extraships set on its own, which of addition and replace gets installed automatically if you ask Oolite to install dependencies for you?". I'm currently leaning towards "pick one arbitrarily" for this.

cim wrote:

The question is "if you install the extraships set on its own, which of addition and replace gets installed automatically if you ask Oolite to install dependencies for you?". I'm currently leaning towards "pick one arbitrarily" for this.

Instead, how about, "ask the person what they want to do"?

List all choices, setting one as the default (often the first listed one is used as default choice)

Here's a method to pass the ownership from one caretaker (CT) to another without bothering cim.

1. The new CT uploads a new version of the OXP into the manager using the same identifier as the old version. At this point there will be two versions of the OXP available.
2. The old CT takes down the old version from the manager.
3. Transfer complete.

To Diziet Sma

Nice guide!
Just uploaded my first OXZ

Need some advice, gentlemen.

I have some package with 50...75 MB graphical content for example.
What way is preferable:
A. To pack all content in one OXZ to avoid issue "you need to download this pack AND additional resource pack too"
B. To pack core OXZ and resource OXZ separately to avoid re-uploading/re-downloading all 75 MB after every minor change in core OXZ
Random Hits, for example, was single pack, later it was split onto core pack and resource pack, now it is single pack again. So I have no clear answer for best solution.
Any guidelines?

stranger wrote: ↑Fri Feb 08, 2019 11:47 pm

To pack core OXZ and resource OXZ separately to avoid re-uploading/re-downloading all 75 MB after every minor change in core OXZ...

That's probably the best option.

Thanks, Cody. Me think too separate packs is better solution.

With many thanks to cim, I am now able to add new users to the Oolite Expansion Pack Manager. Send me a PM and I'll send you back your login details.

Thanks very much, cim and phkb!

Not sure if this has been asked, but how does one indicate dependencies in manifest.plist?

For example I have two separate, but closely related, OXPs in the pipeline, and one must not be used without first installing the other.

When you setup your OXZ for upload to oolite.org, you will be able to enter a dependency using this part of the submission form:



The information will be written to the manifest that oolite.org will create for your oxz and will become part of the collective manifest that the game downloads when you update the OXP list in the Manager.

Ooh, how exciting - thanks again for that one

If you distribute an OXP/OXZ to the public please don't forget a proper license and link, we are facing enough problems here already.

Got it It's the Creative Commons one - version 4.0.