Summary: | [NEW MODULE] bundle.mk: USES=bundle allows bundling ports with the third party submodules | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Yuri Victorovich <yuri> | ||||||||||
Component: | Ports Framework | Assignee: | Port Management Team <portmgr> | ||||||||||
Status: | Closed Overcome By Events | ||||||||||||
Severity: | Affects Only Me | CC: | ports-bugs | ||||||||||
Priority: | --- | Keywords: | feature, needs-qa, patch | ||||||||||
Version: | Latest | ||||||||||||
Hardware: | Any | ||||||||||||
OS: | Any | ||||||||||||
Attachments: |
|
Description
Yuri Victorovich
![]() ![]() Created attachment 163961 [details]
patch
I have something like this on the way, though, a bit simpler. For example, it is simpler to let do-extract extract everything, and then only move things around. If do-extract extracts everything under WRKDIR/, then you need to move the contents of the folders, not the folders themselves. Another custom step. The extract that I suggested looks simpler and more standard. -) Why can't you move the folders ? Because it works just right here. Because the folders are supplied by the parent repository, and they might already have some files in them. If you move the directories, this means you need to delete the originals first with their contents. Why force the additional restrictions? Let authors decide how they bundle things. Created attachment 164186 [details]
patch
Added BUNDLE_ROOT variable.
Created attachment 164803 [details]
patch
This was implemented with GH_SUBDIR. |