I've seen this pop up a lot recently:
* One or more symlinks to directories have been preserved in order to
* ensure that files installed via these symlinks remain accessible. This
* indicates that the mentioned symlink(s) may be obsolete remnants of an
* old install, and it may be
On 01/14/2013 01:33 AM, Dirkjan Ochtman wrote:
I've seen this pop up a lot recently:
* One or more symlinks to directories have been preserved in order to
* ensure that files installed via these symlinks remain accessible. This
* indicates that the mentioned symlink(s) may be obsolete
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/01/13 04:44 AM, Zac Medico wrote:
On 01/14/2013 01:33 AM, Dirkjan Ochtman wrote:
I've seen this pop up a lot recently:
* One or more symlinks to directories have been preserved in
order to * ensure that files installed via these symlinks
On 01/14/2013 06:46 AM, Ian Stakenvicius wrote:
This particular symlink was put there by openrc though, wasn't it?
Yeah, openrc uses the migrate_to_run function from /etc/init.d/bootmisc.
So
I'd expect that on the whole this should be left for openrc to deal
with or otherwise left to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/01/13 09:57 AM, Zac Medico wrote:
On 01/14/2013 06:46 AM, Ian Stakenvicius wrote:
This particular symlink was put there by openrc though, wasn't
it?
Yeah, openrc uses the migrate_to_run function from
/etc/init.d/bootmisc.
So I'd
On 01/14/2013 07:09 AM, Ian Stakenvicius wrote:
On 14/01/13 09:57 AM, Zac Medico wrote:
On 01/14/2013 06:46 AM, Ian Stakenvicius wrote:
This particular symlink was put there by openrc though, wasn't
it?
Yeah, openrc uses the migrate_to_run function from
/etc/init.d/bootmisc.
So I'd
On 01/14/2013 07:44 AM, Zac Medico wrote:
On 01/14/2013 07:09 AM, Ian Stakenvicius wrote:
OK i'm a little confused. Putting my earlier note aside, if the
symlink will be auto-cleaned after no packages use it, what's the
point/need for the original message from portage then?? Is it just QA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/01/13 10:53 AM, Zac Medico wrote:
On 01/14/2013 07:44 AM, Zac Medico wrote:
On 01/14/2013 07:09 AM, Ian Stakenvicius wrote:
OK i'm a little confused. Putting my earlier note aside, if
the symlink will be auto-cleaned after no packages use
On 01/14/2013 08:26 AM, Ian Stakenvicius wrote:
On 14/01/13 10:53 AM, Zac Medico wrote:
On 01/14/2013 07:44 AM, Zac Medico wrote:
On 01/14/2013 07:09 AM, Ian Stakenvicius wrote:
OK i'm a little confused. Putting my earlier note aside, if
the symlink will be auto-cleaned after no packages use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/01/13 11:36 AM, Zac Medico wrote:
On 01/14/2013 08:26 AM, Ian Stakenvicius wrote:
On 14/01/13 10:53 AM, Zac Medico wrote:
On 01/14/2013 07:44 AM, Zac Medico wrote:
On 01/14/2013 07:09 AM, Ian Stakenvicius wrote:
OK i'm a little confused.
On 14/01/2013 18:14, Zac Medico wrote:
It might be a lot simpler to just go and patch all the ebuilds that
installed stuff in /var/run with a one-liner like this at the end of
src_install:
It's a good idea to do so to avoid the check coming from portage to
happena nd waste time, but ...
Once
On 01/14/2013 09:23 AM, Diego Elio Pettenò wrote:
On 14/01/2013 18:14, Zac Medico wrote:
It might be a lot simpler to just go and patch all the ebuilds that
installed stuff in /var/run with a one-liner like this at the end of
src_install:
It's a good idea to do so to avoid the check coming
On 14/01/2013 18:32, Zac Medico wrote:
Ah, right! So, those packages also need to be patched to use /run
directly, instead of relying on the symlink.
Or the symlink should just stay for however long that's going to take,
which is probably a good idea, as it does not bother anyone.
I don't
13 matches
Mail list logo
