10 - support for forcing specific externals into nolib packages
currently, the nolib packages are created by not including externals and commenting out specificaly marked blocks.
There are however some externals that don't exist as standalone addons but which you also don't want to hard-include as a direct copy into your repository. There is currently no way to force these externals into the nolib packages.
So this is a request to add some way to force sepcific externals to be packed even with the nolib zips.
| User | When | Change |
|---|---|---|
| Elkano | Tue, 06 Jan 2009 15:49:40 | Create |
- 2 comments
- 2 comments
Facts
- Last updated on
- 07 Feb 2010
- Reported on
- 06 Jan 2009
- Status
- New - Issue has not had initial review yet.
- Type
- Enhancement - A change which is intended to better the project in some way
- Priority
- Medium - Normal priority.
Reported by
Possible assignees
-
- Manager
- Author
Votes (Total: +61, Average: +2.9)
-
Votes +3
-
Votes +3
-
Votes +3
-
Votes +3
-
Votes +3
-
Votes +3
-
Votes +3
-
Votes +3
-
Votes +3
-
Votes +3
-
Votes +3
-
Votes +3
-
Votes +3
-
Votes +3
-
Votes +3
-
Votes +3
-
Votes +3
-
Votes +3
-
Votes +3
-
Votes +2
-
Votes +2
- #2
StormFX Fri, 07 Aug 2009 04:50:55It could be something as simple as
in the .pkgmeta, which would force the library to be included. That would leave tools-used open for simply allocating points.
P.S. This may also fix the issue with Dewdrop bring down Ace2.
- #1
Tekkub Fri, 24 Jul 2009 06:24:37This is already effecting LDB users... minutes after I posted about LDB being on ace. They have to hard-embed and create a relationship for their project on the web page for things to work. That sucks if you have a bunch of addons...