| 1 |
On Thu, Mar 8, 2018 at 9:11 PM, R0b0t1 <r030t1@×××××.com> wrote: |
| 2 |
> |
| 3 |
> Sadly interest in the patches seems to have waned. The functionality |
| 4 |
> is not exactly duplicated in containers, but they do make it easier to |
| 5 |
> find changes. |
| 6 |
> |
| 7 |
|
| 8 |
Well, the idea with containers wouldn't be to monitor anything, but |
| 9 |
instead to ensure that there is nothing in the container the ebuild |
| 10 |
shouldn't need. If the package declares 3 build-time dependencies |
| 11 |
then the container would contain @system plus those three |
| 12 |
dependencies. If the build system chokes then it will choke for |
| 13 |
everybody (eg for the maintainer testing the package), and not |
| 14 |
randomly when some user doesn't have some package installed that |
| 15 |
wasn't declared. |
| 16 |
|
| 17 |
Now, a container wouldn't help with figuring out what the dependencies |
| 18 |
actually are. Besides inspection/etc a quick solution there is to |
| 19 |
just do a build without a container and check the linking, then go |
| 20 |
back and fix the deps, and then rebuild to verify that nothing else |
| 21 |
was needed. |
| 22 |
|
| 23 |
-- |
| 24 |
Rich |
Archives