| View previous topic :: View next topic |
| Author |
Message |
OldTango
l33t
Joined: 21 Feb 2004
Posts: 718
|
 Posted: Wed Jan 15, 2014 11:55 pm Post subject: Ebuild using Interactive mode can't locate device or files |
 |
|
I have been using Gentoo for ten plus years now and have seen a lot of changes in how cd and dvd drives are handled. When you consider that virtually every computer has at least one of these devices, you would think that by now this would be totally automated and simple, but this dose not appear to be the case. Causing more confusion, the mounting locations when automounting devices in modern desktop environments seem to change. I am using the MATE desktop from the Mate overlay. I have it configured and automounting of media inserted into my dvd drive works. When I insert a disk (video, music or data) it mounts and shows up on my desktop, but I noticed recently that the mounting location has changed from /media to /run/media/my_user_name/name_of_disk. I don't use the drive that often so I don't know when it actually changed or what caused it to change.
The problem is that ebuilds requiring the "Interactive" mode can't locate the device or files. I installed games-fps/yamagi-quake2 from the init6 overlay. I already had all the necessary files on my system so I simply set up the proper directories in my home folder and copied the files to the proper locations. However when playing the add on packs "rogue" and "xatrix" I noticed a lot of stuff is missing from the games. After some more research I determined I needed to install some additional packages.
| Code: |
[ebuild IN ] games-fps/quake2-data-3.20 USE="-videos" 0 kB
[ebuild N ] games-fps/quake2-reckoning-data-1.0::init6 USE="-doc -videos" 0 kB
[ebuild N ] games-fps/quake2-groundzero-data-1.0::init6 USE="-doc -videos" 0 kB
[ebuild N ~] games-fps/yamagi-quake2-rogue-1.07::init6 0 kB
[ebuild N ~] games-fps/yamagi-quake2-xatrix-2.00::init6 0 kB
[ebuild R ~] games-fps/yamagi-quake2-5.10::init6 USE="jpeg openal rogue* vorbis xatrix* zlib -cdinstall -ctf -demo -x11gamma" 0 kB
|
The ebuilds have a DEPEND on games-fps/quake2-data-3.20, but when I try to install this package it fails miserably.
The steps I have tried.
1. Insert Quake2 CD into drive and it gets automounted in /run/media/my_user_name/Quake2
2. emerge games-fps/quake2-data the process starts but then stops with
| Code: |
* This ebuild will need the cdrom for quake2-data
* If you do not have the CD, but have the data files
* mounted somewhere on your filesystem, just export
* the variable CD_ROOT so that it points to the
* directory containing the files.
* For example:
* export CD_ROOT=/mnt/cdrom
* Please insert+mount the cdrom for quake2-data now !
* Press return to scan for the cd again
* or hit CTRL+C to abort the emerge.
|
3. I hit the return key but the ebuild fails to find the CD.
4. Export the CD_ROOT with | Code: | | export CD_ROOT=/run/media/my_user_name/Quake2 |
5. Start the emerge process again and it fails with.
| Code: |
>>> Install quake2-data-3.20 into /var/tmp/portage/games-fps/quake2-data-3.20/image/ category games-fps
!!! dodoc: /run/media/michael/Quake2/Docs/* does not exist
dodoc failed
install: cannot stat ‘/run/media/michael/Quake2/setup/Data/baseq2/pak0.pak’: No such file or directory
!!! doins: /run/media/michael/Quake2/setup/Data/baseq2/pak0.pak does not exist
doins failed
* ERROR: games-fps/quake2-data-3.20::gentoo failed (install phase):
* couldnt grab pak0.pak
*
* Call stack:
* ebuild.sh, line 93: Called src_install
* environment, line 2885: Called die
* The specific snippet of code:
* doins "${baseq2_cdpath}"/pak0.pak || die "couldnt grab pak0.pak";
*
* If you need support, post the output of `emerge --info '=games-fps/quake2-data-3.20::gentoo'`,
* the complete build log and the output of `emerge -pqv '=games-fps/quake2-data-3.20::gentoo'`.
* The complete build log is located at '/var/tmp/portage/games-fps/quake2-data-3.20/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/games-fps/quake2-data-3.20/temp/environment'.
* Working directory: '/var/tmp/portage/games-fps/quake2-data-3.20/work'
* S: '/var/tmp/portage/games-fps/quake2-data-3.20/work'
* QA Notice: file does not exist:
*
* dodoc: /run/media/michael/Quake2/Docs/* does not exist
* doins: /run/media/michael/Quake2/setup/Data/baseq2/pak0.pak does not exist
>>> Failed to emerge games-fps/quake2-data-3.20, Log file:
>>> '/var/tmp/portage/games-fps/quake2-data-3.20/temp/build.log'
|
Based on the errors it looks like there are two problems or bugs in the ebuild.
1. The ebuild fails to locate the device where the cd is inserted.<---- This problem appears to be some built in portage function and probably more difficult to resolve.
2. Using the export command the ebuild fails to locate the files.<---- This seems to be an issue with the ebuild itself and the search paths it is using or resolving to, so it seems like it could be fixed easier.
The quake2-data-3.20 ebuild has this section where I think it is searching the cd for the requested files.
| Code: |
src_install() {
dodoc DOCS/* 3.20_Changes.txt
newdoc ctf/readme.txt ctf-readme.txt
case ${CDROM_SET} in
0) dohtml -r "${CDROM_ROOT}"/Install/DOCS/quake2_manual/* ;;
1) dohtml -r "${CDROM_ROOT}"/Install/Docs/quake2_manual/* ;;
2) dohtml -r "${CDROM_ROOT}"/Install/DOCS/quake2_manual/* ;;
3) dodoc "${CDROM_ROOT}"/Docs/* ;;
esac
local baseq2_cdpath
case ${CDROM_SET} in
0) baseq2_cdpath=${CDROM_ROOT}/baseq2;;
1) baseq2_cdpath=${CDROM_ROOT}/Install/Data/baseq2;;
2) baseq2_cdpath=${CDROM_ROOT}/Install/Data/baseq2;;
3) baseq2_cdpath=${CDROM_ROOT}/setup/Data/baseq2;;
esac
dodir "${GAMES_DATADIR}"/quake2/baseq2
if use videos ; then
insinto "${GAMES_DATADIR}"/quake2/baseq2/video
doins "${baseq2_cdpath}"/video/* || die "doins videos"
fi
insinto "${GAMES_DATADIR}"/quake2/baseq2
doins "${baseq2_cdpath}"/pak0.pak || die "couldnt grab pak0.pak"
doins baseq2/*.pak || die "couldnt grab release paks"
|
The exact errors emerge is reporting are
| Code: |
* dodoc: /run/media/michael/Quake2/Docs/* does not exist
* doins: /run/media/michael/Quake2/setup/Data/baseq2/pak0.pak does not exist
|
I have the full licensed copy of the cd and the paths on the cd are as follows
DOCS ----> /Quake2/Install/Data/DOCS/quake2_manual/
pak0.pak ----? /Quake2/Install/DATA/baseq2/pak0.pak
So what is going on here as I am confused by what I read in the ebuild and the error messages I am getting.
I could file a bug report and wait for some DEV to look into it or wait for it to get fixed, but I would rather find a solution and then submit that solution in a bug report, if it is in fact a bug and not just me doing something stupid.
TIA................ |
|
| Back to top |
|
 |
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22148
|
| Posted: Thu Jan 16, 2014 2:36 am Post subject: |
|
|
| Core Linux never automounts removable media. That is handled by some optional component, likely something in MATE in your case. Blame the maintainers of that program for paths moving over time. Based on what I read in the ebuild, it looks through all mounted filesystems for a filesystem that could be the right type. Please post the output of cat -n /proc/mounts ; ls -la /run/media /run/media/michael/ /run/media/michael/Quake2 as run by the shell that runs emerge unsuccessfully. |
|
| Back to top |
|
|
Genone
Retired Dev
Joined: 14 Mar 2003
Posts: 9565
Location: beyond the rim
|
| Posted: Thu Jan 16, 2014 7:17 am Post subject: Re: Ebuild using Interactive mode can't locate device or fil |
|
|
| OldTango wrote: | | 2. Using the export command the ebuild fails to locate the files.<---- This seems to be an issue with the ebuild itself and the search paths it is using or resolving to, so it seems like it could be fixed easier. |
Locating isn't the problem, I'd guess this is more a permission problem. As the cd is mounted in a user-specific location it's quite possible that this path isn't accessible to portage in src_install. |
|
| Back to top |
|
|
OldTango
l33t
Joined: 21 Feb 2004
Posts: 718
|
| Posted: Thu Jan 16, 2014 2:49 pm Post subject: |
|
|
| Hu wrote: | | Core Linux never automounts removable media. That is handled by some optional component, likely something in MATE in your case. Blame the maintainers of that program for paths moving over time. Based on what I read in the ebuild, it looks through all mounted filesystems for a filesystem that could be the right type. Please post the output of cat -n /proc/mounts ; ls -la /run/media /run/media/michael/ /run/media/michael/Quake2 as run by the shell that runs emerge unsuccessfully. |
Using the MATE terminal logged in as root
| Code: |
1 rootfs / rootfs rw 0 0
2 /dev/sda3 / ext4 rw,noatime,data=ordered 0 0
3 devtmpfs /dev devtmpfs rw,relatime,size=16419048k,nr_inodes=4104762,mode=755 0 0
4 proc /proc proc rw,relatime 0 0
5 tmpfs /run tmpfs rw,nosuid,nodev,relatime,size=3290620k,mode=755 0 0
6 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620 0 0
7 shm /dev/shm tmpfs rw,nosuid,nodev,noexec,relatime 0 0
8 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
9 debugfs /sys/kernel/debug debugfs rw,nosuid,nodev,noexec,relatime 0 0
10 cachedir /lib64/splash/cache tmpfs rw,nosuid,nodev,noexec,noatime,size=4096k,mode=755 0 0
11 /dev/sdb2 /mnt/windows ntfs ro,relatime,uid=0,gid=0,umask=022,nls=utf8,errors=continue,mft_zone_multiplier=1 0 0
12 /dev/sdc1 /home/backup ext3 rw,nosuid,nodev,noexec,noatime,errors=continue,commit=5,barrier=1,data=writeback 0 0
13 /dev/sdd1 /home/shared ext4 rw,nosuid,nodev,noexec,noatime,data=ordered 0 0
14 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0
15 /dev/sr0 /run/media/michael/Quake2 iso9660 ro,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,mode=0400,dmode=0500 0 0
/run/media:
total 0
drwxr-xr-x 3 root root 60 Jan 14 16:58 .
drwxr-xr-x 16 root root 500 Jan 14 16:58 ..
drwxr-x---+ 3 root root 60 Jan 16 07:08 michael
/run/media/michael/:
total 2
drwxr-x---+ 3 root root 60 Jan 16 07:08 .
drwxr-xr-x 3 root root 60 Jan 14 16:58 ..
dr-x------ 1 michael michael 2048 Dec 31 1969 Quake2
/run/media/michael/Quake2:
total 117
dr-x------ 1 michael michael 2048 Dec 31 1969 .
drwxr-x---+ 3 root root 60 Jan 16 07:08 ..
-r-------- 1 michael michael 112 Nov 26 1997 AUTORUN.INF
dr-x------ 1 michael michael 6144 Nov 30 1997 Directx
dr-x------ 1 michael michael 2048 Nov 30 1997 Install
-r-------- 1 michael michael 13350 Nov 29 1997 license.txt
-r-------- 1 michael michael 61630 Nov 29 1997 readme.txt
-r-------- 1 michael michael 31232 Nov 25 1997 Setup.exe
dr-x------ 1 michael michael 2048 Nov 30 1997 Splash
|
Thanks I would like to know what is going on here. |
|
| Back to top |
|
|
OldTango
l33t
Joined: 21 Feb 2004
Posts: 718
|
| Posted: Thu Jan 16, 2014 3:09 pm Post subject: Re: Ebuild using Interactive mode can't locate device or fil |
|
|
| Genone wrote: | | OldTango wrote: | | 2. Using the export command the ebuild fails to locate the files.<---- This seems to be an issue with the ebuild itself and the search paths it is using or resolving to, so it seems like it could be fixed easier. |
Locating isn't the problem, I'd guess this is more a permission problem. As the cd is mounted in a user-specific location it's quite possible that this path isn't accessible to portage in src_install. |
It's starting to look like a permission or access problem to me as well. The mount location really confuses me and I have no idea why or what mounts it there in the first place. I would have thought that running portage as root would give it access to almost any file on my system by default. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22148
|
| Posted: Fri Jan 17, 2014 2:49 am Post subject: Re: Ebuild using Interactive mode can't locate device or fil |
|
|
| OldTango wrote: | | It's starting to look like a permission or access problem to me as well. The mount location really confuses me and I have no idea why or what mounts it there in the first place. I would have thought that running portage as root would give it access to almost any file on my system by default. |
Indeed, and such access is quite dangerous. Therefore, Portage has long had the ability to run substantial portions of the build as a non-root user, so that a package bug cannot do catastrophic damage to your system. Mount your media in a world readable location and try again. |
|
| Back to top |
|
|
OldTango
l33t
Joined: 21 Feb 2004
Posts: 718
|
| Posted: Fri Jan 17, 2014 6:52 pm Post subject: Re: Ebuild using Interactive mode can't locate device or fil |
|
|
| Hu wrote: | | Indeed, and such access is quite dangerous. Therefore, Portage has long had the ability to run substantial portions of the build as a non-root user, so that a package bug cannot do catastrophic damage to your system. Mount your media in a world readable location and try again. |
Thanks for the additional information. I did try several different locations and went as far as | Code: |
mkdir /media/Quake2
mount /dev/sr0 /media/Quake2 |
as root. I could have added some additional mount options which may have worked, but I am attempting to understand why the ebuild can not access the disk or files as written. It didn't seem to matter where or how I mounted the disk and or device the ebuild could not access the files and I am still trying to under stand just what is blocking the process.
I solved the problem by creating, as my user, the necessary directories on a separate drive partition and then coping all the game disks into their appropriate directories. The partition in question is not automounted but has an entry in fstab. Once that was done and I pointed the export command to their locations the emerge process completed without any errors. Permissions on those mounts after their creation is as follows. | Code: |
/home/shared/GameFiles/GameCDs:
total 20
drwxr-xr-x 5 michael michael 4096 Jan 16 10:32 .
drwxr-xr-x 14 michael michael 4096 Jan 16 09:54 ..
drwxr-xr-x 5 michael michael 4096 Jan 16 10:34 Q2GroundZero
drwxr-xr-x 5 michael michael 4096 Jan 16 10:13 Q2TheReckoning
drwxr-xr-x 5 michael michael 4096 Jan 16 09:57 Quake2
/home/shared/GameFiles/GameCDs/Quake2:
total 136
drwxr-xr-x 5 michael michael 4096 Jan 16 09:57 .
drwxr-xr-x 5 michael michael 4096 Jan 16 10:32 ..
-rw-r--r-- 1 michael michael 112 Nov 26 1997 AUTORUN.INF
drwxr-xr-x 3 michael michael 4096 Nov 30 1997 Directx
drwxr-xr-x 3 michael michael 4096 Nov 30 1997 Install
-rw-r--r-- 1 michael michael 13350 Nov 29 1997 license.txt
-rw-r--r-- 1 michael michael 61630 Nov 29 1997 readme.txt
-rw-r--r-- 1 michael michael 31232 Nov 25 1997 Setup.exe
drwxr-xr-x 4 michael michael 4096 Nov 30 1997 Splash
|
This may simply be a case where I am using the MATE desktop which is not ready for prime time yet and I except that problems are going to arise from time to time.
If anyone is interested the /run directory was added some time ago as a tmpfs that gets cleaned on every boot and /var/run is a symlink to /run and still used by some if very few processes. I suspect that /var/run will become obsolete in the near future. More info can be found HERE along with a link to a bug tracker.
| OldTango wrote: | | I noticed recently that the mounting location has changed from /media to /run/media/my_user_name/name_of_disk. I don't use the drive that often so I don't know when it actually changed or what caused it to change. |
For those who may not know this and I didn't until yesterday "/run/media/user_name" is the default location where udisks mounts media. Check HERE for more information.
BTW Yamagi-Quake2 looks and runs better than any other Quake2 client I have ever used in the past.
Thanks Everyone |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22148
|
| Posted: Sat Jan 18, 2014 1:24 am Post subject: Re: Ebuild using Interactive mode can't locate device or fil |
|
|
| OldTango wrote: | | Hu wrote: | | Indeed, and such access is quite dangerous. Therefore, Portage has long had the ability to run substantial portions of the build as a non-root user, so that a package bug cannot do catastrophic damage to your system. Mount your media in a world readable location and try again. |
Thanks for the additional information. I did try several different locations and went as far as | Code: |
mkdir /media/Quake2
mount /dev/sr0 /media/Quake2 |
as root. I could have added some additional mount options which may have worked, but I am attempting to understand why the ebuild can not access the disk or files as written. It didn't seem to matter where or how I mounted the disk and or device the ebuild could not access the files and I am still trying to under stand just what is blocking the process. |
Fixing this sounds like it would be worth pursuing. Could you reproduce this part and reanswer my first round of questions in the context of the new mount? That is, I would like to see /proc/mounts and ls -la /media /media/Quake2. |
|
| Back to top |
|
|
OldTango
l33t
Joined: 21 Feb 2004
Posts: 718
|
| Posted: Sat Jan 18, 2014 4:59 pm Post subject: Re: Ebuild using Interactive mode can't locate device or fil |
|
|
| Hu wrote: | | Fixing this sounds like it would be worth pursuing. Could you reproduce this part and reanswer my first round of questions in the context of the new mount? That is, I would like to see /proc/mounts and ls -la /media /media/Quake2. |
I would be glad to and thanks in advance for all your help.
From my users desktop in the MATE terminal logged in as root I create the mount point and mount the device. | Code: | mkdir /media/Quake2
mount /dev/sr0 /media/Quake2/
mount: /dev/sr0 is write-protected, mounting read-only |
| Code: | ~# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/sda3 / ext4 rw,noatime,data=ordered 0 0
devtmpfs /dev devtmpfs rw,relatime,size=16419048k,nr_inodes=4104762,mode=755 0 0
proc /proc proc rw,relatime 0 0
tmpfs /run tmpfs rw,nosuid,nodev,relatime,size=3290620k,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620 0 0
shm /dev/shm tmpfs rw,nosuid,nodev,noexec,relatime 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,nosuid,nodev,noexec,relatime 0 0
cachedir /lib64/splash/cache tmpfs rw,nosuid,nodev,noexec,noatime,size=4096k,mode=755 0 0
/dev/sdb2 /mnt/windows ntfs ro,relatime,uid=0,gid=0,umask=022,nls=utf8,errors=continue,mft_zone_multiplier=1 0 0
/dev/sdc1 /home/backup ext3 rw,nosuid,nodev,noexec,noatime,errors=continue,commit=5,barrier=1,data=writeback 0 0
/dev/sdd1 /home/shared ext4 rw,nosuid,nodev,noexec,noatime,data=ordered 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0
/dev/sr0 /run/media/michael/Quake2 iso9660 ro,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,mode=0400,dmode=0500 0 0
/dev/sr0 /media/Quake2 iso9660 ro,relatime,uid=1000,gid=1000,iocharset=utf8,mode=0400,dmode=0500 0 0
|
Here is a problem, /dev/sr0 is mounted twice. Once by udisks automount when I inserted the disk from my users desktop and once by root.
| Code: | ~ # ls -la /media /media/Quake2
/media:
total 10
drwxr-xr-x 3 root root 4096 Jan 18 07:49 .
drwxr-xr-x 22 root root 4096 Jan 18 07:47 ..
-rw-r--r-- 1 root root 0 Nov 6 2012 .keep
dr-x------ 1 michael michael 2048 Dec 31 1969 Quake2
/media/Quake2:
total 121
dr-x------ 1 michael michael 2048 Dec 31 1969 .
drwxr-xr-x 3 root root 4096 Jan 18 07:49 ..
-r-------- 1 michael michael 112 Nov 26 1997 AUTORUN.INF
dr-x------ 1 michael michael 6144 Nov 30 1997 Directx
dr-x------ 1 michael michael 2048 Nov 30 1997 Install
-r-------- 1 michael michael 13350 Nov 29 1997 license.txt
-r-------- 1 michael michael 61630 Nov 29 1997 readme.txt
-r-------- 1 michael michael 31232 Nov 25 1997 Setup.exe
dr-x------ 1 michael michael 2048 Nov 30 1997 Splash
|
These permissions appear so strict I don't see how portage could ever access the files. If I issue the umount command which I would have to do twice and then remount the device in /media as root things look much better. | Code: | ~ # umount /dev/sr0 <---- unmounts /media/Quake2
~ # umount /dev/sr0 <---- unmounts /run/media/user_name/Quake2 and removes the icon from my desktop.
~ # mount /dev/sr0 /media/Quake2 <---- mounts the device in a single location and the icon reappears on my users desktop. |
| Code: | ~ # cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/sda3 / ext4 rw,noatime,data=ordered 0 0
devtmpfs /dev devtmpfs rw,relatime,size=16419048k,nr_inodes=4104762,mode=755 0 0
proc /proc proc rw,relatime 0 0
tmpfs /run tmpfs rw,nosuid,nodev,relatime,size=3290620k,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620 0 0
shm /dev/shm tmpfs rw,nosuid,nodev,noexec,relatime 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,nosuid,nodev,noexec,relatime 0 0
cachedir /lib64/splash/cache tmpfs rw,nosuid,nodev,noexec,noatime,size=4096k,mode=755 0 0
/dev/sdb2 /mnt/windows ntfs ro,relatime,uid=0,gid=0,umask=022,nls=utf8,errors=continue,mft_zone_multiplier=1 0 0
/dev/sdc1 /home/backup ext3 rw,nosuid,nodev,noexec,noatime,errors=continue,commit=5,barrier=1,data=writeback 0 0
/dev/sdd1 /home/shared ext4 rw,nosuid,nodev,noexec,noatime,data=ordered 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0
/dev/sr0 /media/Quake2 iso9660 ro,relatime 0 0
|
| Code: | ~ # ls -la /media /media/Quake2
/media:
total 10
drwxr-xr-x 3 root root 4096 Jan 18 07:49 .
drwxr-xr-x 22 root root 4096 Jan 18 07:47 ..
-rw-r--r-- 1 root root 0 Nov 6 2012 .keep
dr-xr-xr-x 1 root root 2048 Dec 31 1969 Quake2
/media/Quake2:
total 121
dr-xr-xr-x 1 root root 2048 Dec 31 1969 .
drwxr-xr-x 3 root root 4096 Jan 18 07:49 ..
-r-xr-xr-x 1 root root 112 Nov 26 1997 AUTORUN.INF
dr-xr-xr-x 1 root root 6144 Nov 30 1997 Directx
dr-xr-xr-x 1 root root 2048 Nov 30 1997 Install
-r-xr-xr-x 1 root root 13350 Nov 29 1997 license.txt
-r-xr-xr-x 1 root root 61630 Nov 29 1997 readme.txt
-r-xr-xr-x 1 root root 31232 Nov 25 1997 Setup.exe
dr-xr-xr-x 1 root root 2048 Nov 30 1997 Splash
|
These permissions are more lax and should allow portage proper access.
I guess I understand the concept of automounting user media in /run/media/user_name/ for security and privacy to a point, but have no idea how "INTERACTIVE" ebuilds will work in a DE with automounting enabled along with the default permissions that get set. Am I missing something here and is my system setup screwed.?
Seems the better approach would be to use the IUSE "cdinstall" use flag which could be turned on or off by the user depending on their particular setup. If I had a better grasp of ebuilds and bash I would submit a new ebuild which would allow this choice. When I consider the number of licensed games I have currently install on my personal system and if they all used "INTERACTIVE" ebuilds, I shutter to think of the trouble I would have, running the "emerge -avuND" command, if several had new updates or USE flag changes at the same time.
Thanks..............  |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
