| 1 |
On 07/26/12 14:26, Rich Freeman wrote: |
| 2 |
> I've been messing around with namespaces and some of what systemd has |
| 3 |
> been doing with them, and I have an idea for a portage feature. |
| 4 |
> |
| 5 |
> But before doing a brain dump of ideas, how useful would it be to have |
| 6 |
> a FEATURE for portage to do a limited-visibility build? That is, the |
| 7 |
> build would be run in an environment where the root filesystem appears |
| 8 |
> to contain everything in a DEPEND (including @system currently) and |
| 9 |
> nothing else? It might be useful both in development/testing, and |
| 10 |
> also in production use (not sure how performance would work in the |
| 11 |
> real world - I was able in a script to get it to build an enviornment |
| 12 |
> in a few seconds for a few packages). |
| 13 |
|
| 14 |
The Cabal build system for Haskell packages does this and it's extremely |
| 15 |
useful. It prevents me from forgetting dependencies like 'directory', |
| 16 |
'time', etc. that I use without thinking. |
| 17 |
|
| 18 |
runghc Setup.hs build |
| 19 |
Building lwn-epub-0.0... |
| 20 |
Preprocessing executable 'lwn-epub' for lwn-epub-0.0... |
| 21 |
|
| 22 |
src/LWN/Article.hs:12:8: |
| 23 |
Could not find module `System.Directory' |
| 24 |
It is a member of the hidden package `directory-1.1.0.2'. |
| 25 |
Perhaps you need to add `directory' to the build-depends in your |
| 26 |
.cabal file. |
| 27 |
Use -v to see a list of the files searched for. |
Archives