The source repositories
This page is for developers who want to change a package, build it again or base their own package on one. The
package server holds only the finished .ezpkg archives; their unpacked source, one folder per package, lives in
separate GitHub repositories of se7enxweb. This page lists them, shows their layout and maps every package of the
6.0.15 index to its repository. Every repository was checked with gh api (read only) on 2026-10-18.
Contents
- The repositories
- The common layout
- The scripts
- Which package comes from where
- Reading a repository
- Related pages
The repositories
| Repository | Package folders in packages/ | Notes |
|---|---|---|
| se7enxweb/sevenx-ezpackage | 14: sevenx_multisite, sevenx_multisite_clean, sevenx_multisite_democontent, sevenx_multisite_democontent_clean, sevenx_site, sevenx_site_clean, sevenx_classes, sevenx_democontent, sevenx_democontent_clean, sevenx_banners, sevenx_design_blue, sevenx_design_cleangray, sevenx_design_gray, sevenx_extension | the 7x packages, among them the default site package; history from 2006, 1226 commits; README and LICENSE since 2026-10-19 |
| se7enxweb/cjw_multisite-ezpackage | 2: cjw_multisite, cjw_multisite_democontent | created 2026-10-07; packed with bin/pack.sh and, since 2026-10-19, packages/build.sh; README and LICENSE since 2026-10-19 |
| se7enxweb/ezwebin-ezpackage | 10: ezwebin_site, ezwebin_site_clean, ezwebin_classes, ezwebin_democontent, ezwebin_democontent_clean, ezwebin_banners, ezwebin_design_blue, ezwebin_design_cleangray, ezwebin_design_gray, ezwebin_extension | a fork of the original vendor's ezwebin |
| se7enxweb/ezflow-ezpackage | 7: ezflow_site, ezflow_site_clean, ezflow_classes, ezflow_democontent, ezflow_democontent_clean, ezflow_design, ezflow_extension | a fork of ezflow |
| se7enxweb/ezdemo-ezpackage | 6: ezdemo_site, ezdemo_site_clean, ezdemo_classes, ezdemo_democontent, ezdemo_democontent_clean, ezdemo_extension | a fork of ezdemo |
| se7enxweb/ezpaypal-ezpackage | 1: ezpaypal_extension | has a README.md |
| se7enxweb/ezstarrating-ezpackage | 1: ezstarrating_extension | a fork of ezstarrating |
| se7enxweb/ezgmaplocation-ezpackage | 1: ezgmaplocation_extension | a fork of ezgmaplocation; no packages/build.sh |
| se7enxweb/ezwt-ezpackage | 1: ezwt_extension | a fork of ezwt; no packages/build.sh |
| se7enxweb/ezcomments-ezpackage | 1: ezcomments_extension | a fork of ezcomments; this package is not in the 6.0.15 index |
The old package folders of the 3.x to 5.x releases, no longer on the server, are kept in se7enxweb/deprecated.ezpublish.packages.ezpublish.one.
Note
plain_site is on the package server but is not in any of these repositories. To change it, start from the
.ezpkg itself (Downloading a package by hand).
The common layout
sevenx-ezpackage and cjw_multisite-ezpackage have this layout, and so do ezwebin, ezflow, ezstarrating,
ezgmaplocation and ezwt (ezflow-ezpackage also has doc/). ezdemo-ezpackage, ezpaypal-ezpackage and
ezcomments-ezpackage have only packages/ (plus web files in ezdemo-ezpackage and a README.md in
ezpaypal-ezpackage). build.sh is in seven of them: sevenx, cjw_multisite (since 2026-10-19), ezwebin, ezflow, ezdemo,
ezpaypal and ezstarrating.
packages/
build.sh packs every folder into <folder>.ezpkg
<name>/ one package, unpacked
package.xml the definition
documents/LICENCE the license text
files/default/... thumbnail and other files
settings/... install scripts of a site package
ezcontentclass/... classes of a contentclass package
ezextension/... the extension of an extension package
bin/
pack.sh packs every folder, into --output-dir
repack_extension.sh rebuilds an extension package from an installation
ezpxmlextfilelist.php lists the files of an extension directory (-e <extension>)
ant/
createzpkg.sh packs one folder
ezwebin.propertiesWhat goes into each kind of package folder is described in What a site installer package is and The .ezpkg file.
The scripts
| Script | What it does | Leaves out |
|---|---|---|
packages/build.sh | run inside packages/: for each folder, tar -zcf ../<folder>.ezpkg of its content, so the .ezpkg files land next to the folders | .git, .gitignore, .gitattributes, .gitmodules, .svn, .hg, .DS_Store, .idea, .vscode, node_modules, *~, *.swp; in the 7x and CJW repositories also *.bak and *.bak.* (since 2026-10-19) |
bin/pack.sh | run from the repository root: packs each folder of packages/ except package_set into --output-dir=<dir> (default /tmp/ezwebin/packages) | the same list, plus .cache and pack_and_publish.bat |
ant/createzpkg.sh | createzpkg.sh <source> <destination>: packs one folder into <destination>.ezpkg | .svn, .cache, pack_and_publish.bat |
bin/repack_extension.sh | --with-ezp=<dir>: recreates the extension package from an installation; the result lands in var/storage/packages/local/ |
The archive's top level is the package folder's content, so package.xml is at the top of the .ezpkg, as the
importer expects. build.sh came to sevenx-ezpackage on 2026-10-14 ("The package build script, which leaves version
control folders and editor files out of every package"). How to use it: Rebuilding with build.sh.
Warning
Give bin/pack.sh an --output-dir of your own. Its default lies in the system's shared temporary folder.
Which package comes from where
| Packages of the 6.0.15 index | Repository |
|---|---|
sevenx_* (14) | sevenx-ezpackage |
cjw_multisite, cjw_multisite_democontent | cjw_multisite-ezpackage |
ezwebin_* (10) | ezwebin-ezpackage |
ezflow_* (7) | ezflow-ezpackage |
ezdemo_* (6) | ezdemo-ezpackage |
ezpaypal_extension, ezstarrating_extension, ezgmaplocation_extension, ezwt_extension | their own -ezpackage repository each |
plain_site | none of these |
That is 43 of the 44 packages of the 6.0.15 index.
Reading a repository
# the folders and their history, without a full checkout of large binaries
git clone --filter=blob:none https://github.com/se7enxweb/sevenx-ezpackage.git
cd sevenx-ezpackage
ls packages/
git log --oneline -- packages/sevenx_multisiteCommit messages in these repositories start with Added:, Updated:, Removed: or Renamed: and name the package,
for example "Updated: The installer of the sevenx_site package activates ezownerchange, so changing the owner of
content is available in a new installation". The same change then appears as a separate commit on the package server
(How a release reaches the package server).
To change a package for yourself, fork its repository (Forking a site package); to change it for everyone, open a pull request there, and for a new package see Contribute your site package.
Related pages
- Site packages: start here
- The package server
- How a release reaches the package server
- The package server on GitHub
- Making your own site package
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.