History of PackagerPackage
Version 2 | Current version | |
---|---|---|
PackagePlease enter the name of the package you are uploading. You can use whatever name you like, but please bear in mind that the name will be converted to lower case and that any special characters will be removed.VersionVersioning in bitweaver follows some basic rules. The version numbers are split into 3 distinct parts major.minor.trivial.status where every segment has it's own purpose. Here is a brief description of how version numbers are assigned to the core packages in bitweaver:
Version is set in your admin/schema_inc.php file: Setting the Package Version
Core packagesCore packages are required packages in bitweaver. These packages are considered core and bitweaver will not work without these:
Package TypePackage creation in bitweaver is quite simple and therefore there are many different packages that are available. Grouping packages into their types makes it easy for other users to find a package of a given typePackage descriptionThis should contain a brief summary of your package, what it does and what if provides. You can provide extensive documentation elsewhere and provide a link to that place using the Documentation URL enty field.Documentaion URLIf you have set up a website with more information about this package, please provide it here.Upload PackageChose the package archive you wish to upload. The name of the file is irrelevant since it will be renamed using the information provided above. The final filename will be:<package name="">-<version>-<status>.tar.gz the archives you upload will be extracted and checked for a few required parameters. Firstly, the package needs to be contained in a folder within the archive. For packages to work in bitweaver, the bit_setup_inc.php file is required and will therefore be searched for. If this file does not exist, the package is considered non-functional and will be discarded. AuthorEnter the name of the author or provide a valid email address.Maintainer URLThis can be a url to a website where more information about the package is provided.LicensePick a license appropriate for your package.Security ReleaseOnly check this box if the release is a security release. This will highlight the package in the package manager and alert the user that there are important upgrades available.ServiceOnly check this box if the package you are providing is a true service to other packages such as categorisation.RequirementsHere you can enter the requirements or your package. to specify a requirement of a certain version of the core packages, please use kernel for this.Requirements format
this will indicate that the package being uploaded works with kernel from version 2.0.1 to version 2.1.1 and with wiki of versions between 0.2.1.pl and 0.3.0. ChangelogThe changelog should be provided as a textfile which will be interpreted after the upload. Every line should contain one entry. Lines that don't start with +, - or ! will be ignored. If you keep a log file spanning multiple versions, please separate versions using <version>.<status> as set in the version section.
Changelog format
Planson creation of package details, we link to or create wiki page with <package>Package title and ask author to provide some information therecreate service that we can display packager_details in wiki specific wiki page as set by bwo_content_id DevelopersHere are a few points to keep in mind when creating an upgrade file:
Using the code below, and upgrading from 0.0.0 to 0.0.4 the upgrade process would include in this order:
Valid upgrade file setup
</package></status></version></status></version></package> | PackagePlease enter the name of the package you are uploading. You can use whatever name you like, but please bear in mind that the name will be converted to lower case and that any special characters will be removed.VersionVersioning in bitweaver follows some basic rules. The version numbers are split into 3 distinct parts major.minor.trivial.status where every segment has it's own purpose. Here is a brief description of how version numbers are assigned to the core packages in bitweaver:
Version is set in your admin/schema_inc.php file: Setting the Package Version
Core packagesCore packages are required packages in bitweaver. These packages are considered core and bitweaver will not work without these:
Package TypePackage creation in bitweaver is quite simple and therefore there are many different packages that are available. Grouping packages into their types makes it easy for other users to find a package of a given typePackage descriptionThis should contain a brief summary of your package, what it does and what if provides. You can provide extensive documentation elsewhere and provide a link to that place using the Documentation URL enty field.Documentaion URLIf you have set up a website with more information about this package, please provide it here.Upload PackageChose the package archive you wish to upload. The name of the file is irrelevant since it will be renamed using the information provided above. The final filename will be:<package name="">-<version>-<status>.tar.gz the archives you upload will be extracted and checked for a few required parameters. Firstly, the package needs to be contained in a folder within the archive. For packages to work in bitweaver, the bit_setup_inc.php file is required and will therefore be searched for. If this file does not exist, the package is considered non-functional and will be discarded. AuthorEnter the name of the author or provide a valid email address.Maintainer URLThis can be a url to a website where more information about the package is provided.LicensePick a license appropriate for your package.Security ReleaseOnly check this box if the release is a security release. This will highlight the package in the package manager and alert the user that there are important upgrades available.ServiceOnly check this box if the package you are providing is a true service to other packages such as categorisation.RequirementsHere you can enter the requirements or your package. to specify a requirement of a certain version of the core packages, please use kernel for this.Requirements format
this will indicate that the package being uploaded works with kernel from version 2.0.1 to version 2.1.1 and with wiki of versions between 0.2.1.pl and 0.3.0. ChangelogThe changelog should be provided as a textfile which will be interpreted after the upload. Every line should contain one entry. Lines that don't start with +, - or ! will be ignored. If you keep a log file spanning multiple versions, please separate versions using <version>.<status> as set in the version section.
Changelog format
Planson creation of package details, we link to or create wiki page with <package>Package title and ask author to provide some information therecreate service that we can display packager_details in wiki specific wiki page as set by bwo_content_id DevelopersHere are a few points to keep in mind when creating an upgrade file:
Using the code below, and upgrading from 0.0.0 to 0.0.4 the upgrade process would include in this order:
Valid upgrade file setup
</package></status></version></status></version></package> |