#5612 closed enhancement (fixed)
Create a build rule for archiving Haiku's local sources
| Reported by: | mmadia | Owned by: | bonefish |
|---|---|---|---|
| Priority: | normal | Milestone: | R1/beta2 |
| Component: | Build System | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Similar to #5110 and #5482, this proposed rule would compress the local source repository and add it to the image. This would be activated on configure --include-sources or HAIKU_INCLUDE_SOURCES = 1 . The new rule would exclude repository specific folders (.svn, .hg, .git) and generated* from the archive. The source archive would be installed via a rule similar to InstallSourceArchive -- perhaps modify that rule to treat <file> as an absolute path when <url> is not provided.
Though, I'm uncertain how the buildtools repository would be handled.
If this is an acceptable enhancement, please re-assign to me.
Change History (6)
follow-up: 2 comment:1 by , 15 years ago
comment:2 by , 15 years ago
Replying to bonefish:
I suppose the intended use is for (L)GPLed software that won't be outsourced?
Yes. My intention is for the build system to become capable of creating image files that contain all of its utilized sources. Those images would be ideal for distributing Haiku on physical mediums -- selling official CD's or even handing out cheap freebies at conferences. By providing all of the sources on the physical medium, we won't need to concern ourselves with providing written offers of source code nor responding to them. Though IIRC for GPLv3, we'd need to provide instructions in addition to the sources.
comment:3 by , 10 years ago
Is there anything left in Haiku sources that uses one of those licenses? We are outsourcing as much as possible now. Still, the release media should probably include the source packages for those GPL and LGPL software.
comment:4 by , 10 years ago
Yes, GDB & Libintl & Awk are still in-tree. They can't be removed until we write a recipe for the in-tree version of GDB and add the in-tree patches to it.
comment:5 by , 6 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This was done in c20e7a686272e84.
comment:6 by , 5 years ago
| Milestone: | R1 → R1/beta2 |
|---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
I suppose the intended use is for (L)GPLed software that won't be outsourced? While we have quite a bit of those, it seems overkill to include the whole sources even when excluding src/{build,test,tools}. OTOH we even had to include the src/{build,tools}, since those are part of the build system for the (L)GPL packages. Not sure how to handle this best. Though including the complete sources in a regular image isn't practical IMHO.