371
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: + + + + + + + + + + + + + + + + + + Line 260:
Line 278: − + + + + + Line 274:
Line 296: − + − + + + − *README.md - change name and add link to bugzilla for both new and existing names (i.e. keep the old link there)+ −
Add info about script to do this
This page is to discuss and track the migration of legacy e-smith- packages etc. to smeserver- packages and the associated changes required.
This page is to discuss and track the migration of legacy e-smith- packages etc. to smeserver- packages and the associated changes required.
This is now being done via a script (rename-e-smith-pkg.git, held in the smeserver-gitutils repo on [https://src.koozali.org/smedev/smeserver-gitutils https://src.koozali.org])
It uses the smeserver-gitutils config files (~/.smegit/config)
=== rename-e-smith-pkg.sh ===
Rename an e-smith package as smeserver and change relevant files<syntaxhighlight lang="bash">
rename-emith-pkg.sh <pkg> [<organisation> <local> <force> <debug>]
</syntaxhighlight><pkg> = Module name e.g. e-smith-dnscache
optional parameters, can appear in any order
* <organisation> (any gitea organisation smeserver, smecontribs or user - defaults to smeserver)
* <local> will use parameters set for local repository else it will use remote
* <force> will automagically delete an existing repo, otherwise it will prompt
* <debug> run in debug mode
This works whether the repo and local files exist of not (it deletes them if necessary)
{| class="wikitable"
{| class="wikitable"
|+List of base e-smith packages
|+List of base e-smith packages
=== What needs to be done:===
=== What needs to be done:===
All of these changes are being done in the new https://src.koozali.org GITEA instance after the packages have been migrated there.
All of these changes are being done from the new https://src.koozali.org GITEA instance after the packages have been migrated there.
The following actions are being performed by the script:
*Fork the e-smith-<pkg> into your own user space as <user>/smeserver-<pkg>
*Fork the e-smith-<pkg> into your own user space as <user>/smeserver-<pkg>
*README.md - change name and add link to bugzilla for both new and existing names (i.e. keep the old link there)
*Makefile - change e-smith to smeserver
*Makefile - change e-smith to smeserver
.
.
Provides: e-smith-<pkg>
Provides: e-smith-<pkg>
</syntaxhighlight>change all Requires: e-smith- to Requires: smeserver-<br>If the Source: is not tar.gz, change it and delete the archivefilename file<syntaxhighlight lang="spec">
</syntaxhighlight>change all Requires:& BuildRequires: e-smith- to Requires: or BuildRequires: smeserver-<br>If the Source: is not tar.gz, change it and delete the archivefilename file<syntaxhighlight lang="spec">
Source: %{name}-%{version}.tar.gz
Source: %{name}-%{version}.tar.gz
</syntaxhighlight>add entry to changelog and reference Bugzilla bug #12359
</syntaxhighlight>change e-smith to smeserver for Summary: and %description
add entry to changelog and reference Bugzilla bug #12359
*createlinks - you may need to change the update event to smeserver- (from e-smith)
*createlinks - you may need to change the update event to smeserver- (from e-smith)
There is no API function for the 'Convert to a Regular Repository' action, so the following will need to be performed manually via the GITEA web interface.
*'Convert to a Regular Repository'
*'Convert to a Regular Repository'
*'Transfer' your smeserver-<pkg> over to the smeserver Organisation (owner) when you think it's ready for review/testing/etc.
*'Transfer' your smeserver-<pkg> over to the smeserver Organisation (owner) when you think it's ready for review/testing/etc.