Editing Packaging

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
 
The packaging system uses the [http://www.cygwin.com/ Cygwin] packaging system through the [http://www.cygwin.com/setup.exe setup.exe] software, which allows package download, installation, version management, etc...
 
The packaging system uses the [http://www.cygwin.com/ Cygwin] packaging system through the [http://www.cygwin.com/setup.exe setup.exe] software, which allows package download, installation, version management, etc...
  
This software isn't supposed to be used for anything else than installing Cygwin, although we can cheat with it in order to manage [[Orbiter|Orbiter]] packages.
+
This software isn't supposed to be used for anything else than installing Cygwin, although we can cheat with it in order to manage Orbiter packages.
  
 
=How can I use it?=
 
=How can I use it?=
Line 30: Line 30:
  
 
You can browse http://construct.ath.cx/~case/orbiter/repository/ and see how it's organised.
 
You can browse http://construct.ath.cx/~case/orbiter/repository/ and see how it's organised.
 
http://sourceware.org/cygwin-apps/package-server.html
 
 
=Discution about package organisation=
 
 
==Basic Rules==
 
 
* A package can't have a file with the same name at the same place than another package.
 
* A package will have the less dependencies possible, i.e :
 
** '''Vessels''' will never depend on bases, other vesseles, mfd's, etc... If a scenario involving this vessel need other addons, this scenario will be hosted in a separate package. So if someone want to play a certain mission, he will install the scenario and all its dependencies (including the vessel), if we only want to install the vessel only, he still can. the scenario shipped with a vessel must work with orbiter_base alone.
 
** '''Bases''' packages will never depend on vessels, systems, or anything. But a lot of systems can be created, some of them sharing the same bases.
 
 
[[Category: Articles]]
 
[[Category: Tutorials]]
 

Please note that all contributions to OrbiterWiki are considered to be released under the GNU Free Documentation License 1.2 (see OrbiterWiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:

Cancel Editing help (opens in new window)