[WIP] Systemize/make a meaningful component from the project #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jnpkrn
force-pushed
the
systemize
branch
3 times, most recently
from
991e7f2
to
cb0a136
Compare
... that got lost in "Convert Resource Agent API to markdown" commit. Some tweaks are due before claiming it's anywhere close to accordance with practical application (cf. /usr/ocf vs. /usr/lib/ocf). Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
Specific, i.e., self-contained approach is used to carry formal, typically machine readable data (that are best maintained in a discrete form) bound to particular minor version, while common, i.e., accumulative approach with subsequent (and properly annotated for that matter) additions as the standard evolves through its minor versions is natural for documentation-like files for persual by technical people that are presumably familiar with such iterative documentation. Note that even the latter type of content will have a separate representation in such a versioning scheme, allowing for legacy-less progression (as across and only across major versions the disruptive changes are anticipated). This scheme, detailed in ra/README, also allows us to drop redundant files, only to be reintroduced when "next" becomes backward incompatible (in terms of the schema for the metadata), because "next" directory now belongs under existing "api-1" branch. Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
jnpkrn
force-pushed
the
systemize
branch
4 times, most recently
from
832efae
to
4e08049
Compare
Making some minor cleanup to existing Makefile along the way. Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
This solves following constraint: > GNU make allows only one recipe to be specified per target Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
(some commentary TBD) Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
|
Creating an installable component for OCF as a project periodically arises as an idea, and will likely be worth pursuing. The idea of generating include files for multiple languages from a single authoritative source is interesting as well. However I don't think we are ready to delineate what belongs in a packageable component yet, or what dependencies we're willing to apply to other ClusterLabs projects. Leaving this for future consideration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.