Difference between revisions of "Migrate e-smith to smeserver"

From SME Server
Jump to navigationJump to search
m
m
Line 267: Line 267:
 
</syntaxhighlight>
 
</syntaxhighlight>
  
* README.md - change name and link to bugzilla
+
* README.md - change name and add link to bugzilla for both new name (keep the old link there)
  
 
* Transfer your smeserver-<pkg> over to the smeserver Organisation when you think it's ready for review/testing/etc.
 
* Transfer your smeserver-<pkg> over to the smeserver Organisation when you think it's ready for review/testing/etc.
Line 293: Line 293:
  
 
Whilst the changes in the root directory structure are fairly obvious, this also impacts the createlinks file
 
Whilst the changes in the root directory structure are fairly obvious, this also impacts the createlinks file
 +
[[Category:Developer]]

Revision as of 07:32, 18 May 2023

This page is to discuss and track the migration of legacy e-smith- packages etc. to smeserver- packages and the associated changes required.

List of base e-smith packages
Package Status Who Comments
e-smith draft TrevorB
e-smith-LPRng
e-smith-apache
e-smith-backup draft TrevorB
e-smith-base
e-smith-cvm-unix-local
e-smith-devtools draft TrevorB
e-smith-dnscache
e-smith-domains
e-smith-dynamicdns-dyndns
e-smith-dynamicdns-dyndns.org
e-smith-dynamicdns-tzo
e-smith-dynamicdns-yi
e-smith-email draft TrevorB
e-smith-flexbackup
e-smith-formmagick
e-smith-grub
e-smith-horde
e-smith-hosts
e-smith-ibays
e-smith-imp
e-smith-ingo
e-smith-ldap
e-smith-lib draft TrevorB
e-smith-lib-compspec
e-smith-manager
e-smith-mysql
e-smith-ntp
e-smith-nutUPS
e-smith-oidentd
e-smith-openssh
e-smith-packetfilter
e-smith-php
e-smith-po
e-smith-portforwarding
e-smith-pptpd
e-smith-proftpd
e-smith-proxy
e-smith-qmail
e-smith-qmailanalog
e-smith-quota
e-smith-radiusd
e-smith-runit
e-smith-samba
e-smith-starterwebsite
e-smith-test
e-smith-tinydns
e-smith-turba
e-smith-viewlogfiles

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.

  • Create copy of e-smith-<pkg> as smeserver-<pkg> Fork the smeserver/e-smith-<pkg> into your own user space as <user>/smeserver-<pkg>
  • Makefile - change e-smith to smeserver
    NAME := smeserver-<pkg>
    
  • smeserver-<pkg>.spec - change e-smith to smeserver and add in Provides of the old e-smith package
    %define name smeserver-<pkg>
    
    Provides: e-smith-<pkg>
    
    If the Source: is not tar.gz change it and delete the archivefilename file
    Source: %{name}-%{version}.tar.gz
    
  • README.md - change name and add link to bugzilla for both new name (keep the old link there)
  • Transfer your smeserver-<pkg> over to the smeserver Organisation when you think it's ready for review/testing/etc.

Do we need to change the e-smith directories too?

In the first few packages I 'migrated' I have also change the standard e-smith directories to smeserver and created a symlink of the old e-smith directory to the new smeserver one, to support the old structure.

new smeserver directories
directory where initialised
/etc/smeserver smeserver-lib
/home/e-smith
/usr/sbin/smeserver smeserver-lib
/usr/local/perl5/vendor_perl/esmith smeserver-devtools

In the packages I have 'migrated' I have also changed the directory structure to fit this new model.

Whilst the changes in the root directory structure are fairly obvious, this also impacts the createlinks file