[Bug 449135] Review Request: gforge - GForge Collaborative Development Environment

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=449135





--- Comment #17 from Andrea Musuruane <musuruan@xxxxxxxxx>  2008-08-06 04:10:48 EDT ---
(In reply to comment #16)
> Regarding the way to hardcoding any password in the package, I'm thinking about
> writing a helper script that must be run by superuser and performs that task
> after the package has been installed. The point is the proper way to inform
> about it. Issuing a message on %post might be unnoticed by many users. Mailing
> to root account sounds better, but might not be correctly redirected. And
> adding that into a README/ENABLE file on %doc does not appear as a better
> solution to me.
> Any ideas ?

The Fedora way is a README.Fedora file in %doc. It is used by many packages and
that is what an admin should look for after installing if manual intervention
is needed.

https://fedoraproject.org/wiki/Packaging/Guidelines#summary

-- 
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.

_______________________________________________
Fedora-package-review mailing list
Fedora-package-review@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-package-review

[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]