You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/comparisons/utility/package_templates.md
+49-2Lines changed: 49 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,12 +11,59 @@ There are several ways to create a Julia packages from templates.
11
11
### PkgTemplates.jl
12
12
{{badge PkgTemplates}}
13
13
14
+
> Create new Julia packages, the easy way
15
+
14
16
This package is the the most popular package generator.
15
17
18
+
It helps you set up the package structure, git repository, CI automations for building documentation, running tests, checking code coverage and more.
19
+
20
+
### PackageMaker.jl
21
+
{{badge PackageMaker}}
22
+
23
+
> GUI for PkgTemplates.jl: "Creating new Julia packages, the easy way" - made a bit simpler.
24
+
25
+
From the package README:
26
+
27
+
This package allows you to create either a new package or a new project.
28
+
It implements a subset of [PkgTemplates.jl](https://github.com/JuliaCI/PkgTemplates.jl) features (which subset hopefully covers >90% of its use cases).
29
+
It also adds a couple of features of its own, e.g. ability to create Julia projects, or adding dependencies to projects or packages being created.
30
+
Being a GUI app, it should be mostly self-explanatory, and external links for more information are provided from the GUI, too.
31
+
16
32
### PkgSkeleton.jl
17
33
{{badge PkgSkeleton}}
18
34
19
-
PkgSkeleton is another package generator.
35
+
> Generate Julia package skeletons using a simple template system
36
+
37
+
From the package README:
38
+
39
+
Julia package for creating new packages and updating existing ones, following common practices and workflow recommendations.
40
+
41
+
Design principles:
42
+
43
+
* Keep it simple: do nothing more than substitute strings into templates, with a few safeguards. This keeps the code simple: currently less than 300 LOC without docstrings. For me, this covers 99% of the use cases; the rest I edit manually.
44
+
* Tread ligthly: don't modify uncommitted files (unless asked to, but really don't do that), or files with the same content (to preserve timestamps).
45
+
* Assume that tooling for packages will keep changing, make it easy to update.
0 commit comments