[Bug 249949] Review Request: beldi - Belug Linux Distribution Burner
bugzilla at redhat.com
bugzilla at redhat.com
Wed Sep 19 14:11:50 UTC 2007
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Review Request: beldi - Belug Linux Distribution Burner
https://bugzilla.redhat.com/show_bug.cgi?id=249949
------- Additional Comments From fedora at christoph-wickert.de 2007-09-19 10:11 EST -------
(In reply to comment #8)
> Okay, I've to slap upstream. Changing source is worse, but this is an upstream
> issue, not downstream.
Yes, it's an upstream issue, but it makes tracking changes for us (you as the
maintainer) harder. :(
> But Beldi should take $HOME/beldi or something per
> default as only one user per machine normally really uses Beldi.
And how do you want achieve this if not with userhelper?
> Independent of
> this, Beldi can given another parameter to use a common location for the files
> it uses.
$HOME/beldi is a bad idea I think, because it can interfere with
system-config-users (in the unlikely case someone creates a user called "beldi")
/var/lib/beldi is better and follows the FHS.
If we use $HOME/beldi we _need_ to create the beldi user during %post.
> Removing the qemu requirement again is nothing big.
Removing qemu from Requires: is no big deal but it leaves us with the "Test with
qemu" button.
> Suid is what upstream would
> like to avoid. Upstream prefers either separate directories or one directory
> which is read-writable to all users. The last of these solutions is discouraged
> in Fedora as I got from #fedora-devel.
I wasn't suggesting to make beldi suid or creating a world writable directory
but about using userhelper like we do for revisor and other tools. To me this is
the best solution, the "fedora way": It guarantees that beldi always is executed
as a certain user, so that all users can share a single beldi installation.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the package-review
mailing list