Byte code compilation
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 485
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
Looks good, I'd love our package management processes to get more mature. Many moons ago we developed a basic packaging system for use internally. Nothing at even this level, just something basic which we could use with ansible to version and deploy our code.
One thing we did is integrate bytecode compilation into our process. Effectively the way we did it was with a package step, that similarly to this produces compressed tar balls. Then on the relevant server an installation utility which extracts the code into a directory, then compiles each file, putting the output into a merged directory.
Any thoughts on this?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Review the described packaging flow—compressed tarballs, an installation utility, and compilation into a merged directory—and clarify the desired scope before implementation; done would require an agreed bytecode-compilation design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, lua
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100