'everything' install option in FC5test1
by Marius Andreiana
Hi,
Please see bug
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=174092
It seems that with Everything install option gone in FC5 test1, one
cannot install all packages from CD. I'm still downloading it so I
cannot test by myself yet, but Jeremy's reply suggests it won't be added
back (how are the package groups handled with multiple repositories?).
In previous Fedora versions, there was also the Details button for a
package group, is this gone too? There one could have manually selected
additional packages, and this is a solution.
If both these options are gone, then should the packages which aren't
installed by default if all groups are selected be moved to Fedora
Extras?
Thanks,
--
Marius Andreiana
18 years, 5 months
- 11
- 25
[Warning] Building new D-Bus packages tomorrow
by John (J5) Palmieri
I'm going to be building 0.60 into rawhide tomorrow. There is some API
and ABI changes so the sonames have been incremented. This means any
application using D-Bus will have to be recompiled and in some instances
code will have to be changed. The API change to look out for is when
requesting names the flags have changed and semantics have changed also.
There are now three RequestName flags and four results that can be
returned. The flags are:
#define DBUS_NAME_FLAG_ALLOW_REPLACEMENT 0x1
#define DBUS_NAME_FLAG_REPLACE_EXISTING 0x2
#define DBUS_NAME_FLAG_DO_NOT_QUEUE 0x4
ALLOW_REPLACEMENT states that another service can replace your service
as the primary owner of the name.
REPLACE_EXISTING states that if there is already a primary owner try to
replace it
DO_NOT_QUEUE states that if your service can not be the primary owner
(i.e. there already is one that does not ALLOW_REPLACEMENT) then have
RequestName fail instead of putting your service into the queue
The results returned by RequestName are as follows:
#define DBUS_REQUEST_NAME_REPLY_PRIMARY_OWNER 1
#define DBUS_REQUEST_NAME_REPLY_IN_QUEUE 2
#define DBUS_REQUEST_NAME_REPLY_EXISTS 3
#define DBUS_REQUEST_NAME_REPLY_ALREADY_OWNER 4
PRIMARY_OWNER indicates you have become the primary owner
IN_QUEUE indicates you have been placed in the queue
EXISTS indicates you are already in the queue
ALREADY_OWNER indicates you are already the primary owner
--
John (J5) Palmieri <johnp(a)redhat.com>
18 years, 5 months
- 1
- 1
custom selinux policy
by Laurent Jacquot
Hello,
I can no longer build my custom selinux policy with recent upgrades (SE
policy source replaced with SE policy).
What is the new way (used to be make reload)?
tx in advance
jk
18 years, 5 months
- 3
- 8