| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Saturday 04 October 2003 03:56 pm, Patrick Börjesson wrote: |
| 5 |
> That would mean that portage wouldn't be able to track the files |
| 6 |
> installed when doing a "make install" on those packages... As the |
| 7 |
> kernels don't install anything, but in /lib/modules/`uname -r` where the |
| 8 |
> kernel-modules go, portage doesn't have to track the files generated by |
| 9 |
> a kernel-compile. But to be able to remove files which ordinary packages |
| 10 |
> install portage has to be able to track the files installed by those |
| 11 |
> packages. This would mean that portage would have to be extensively |
| 12 |
> modified to be able to handle the files installed by a "make install" |
| 13 |
> from a package merged to /usr/src. |
| 14 |
> Just a thought... |
| 15 |
In theory, Portage could track them if ebuild could be modified to use /usr/ |
| 16 |
src/pkg when it existed instead of /var/tmp/portage/*/work and the |
| 17 |
application was installed via 'ebuild pkg merge'. I'm not sure how possible |
| 18 |
that would be for implementation, though. |
| 19 |
- -- |
| 20 |
Luke-Jr |
| 21 |
Developer, Gentoo Linux |
| 22 |
http://www.gentoo.org/ |
| 23 |
-----BEGIN PGP SIGNATURE----- |
| 24 |
Version: GnuPG v1.2.3 (GNU/Linux) |
| 25 |
|
| 26 |
iD8DBQE/fwOKZl/BHdU+lYMRAqTcAJ0e56vTbTmiQPT216LyFjnFCgG2BACfUHty |
| 27 |
HOTJtpID3o1hsZek1664yvs= |
| 28 |
=bY6v |
| 29 |
-----END PGP SIGNATURE----- |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-dev@g.o mailing list |
Archives