Editing Porters Guideline
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 16: | Line 16: | ||
When creating ports, it is crucial to ensure that ports do not change or override a file from other ports, including config files. All files that a port install must be tracked in the pkg-plist file and/or the Makefile except config files. Most of the time, a config file is a .conf file. A useful tool to use to verify the port is to norm is portlint. | When creating ports, it is crucial to ensure that ports do not change or override a file from other ports, including config files. All files that a port install must be tracked in the pkg-plist file and/or the Makefile except config files. Most of the time, a config file is a .conf file. A useful tool to use to verify the port is to norm is portlint. | ||
| − | == Guideline to maintain Ports == | + | == Guideline to maintain Ports. == |
| − | Maintaining ports for GhostBSD is basically follow the same rules than creating ports. | + | Maintaining ports for GhostBSD is basically follow the same rules than creating ports. |
== Guideline to resynced Ports from FreeBSD == | == Guideline to resynced Ports from FreeBSD == | ||
