Charles Dostale wrote:
MySQL and PostgreSQL come to mind.
/etc/yum.conf might have nodowngrade=mysql-server postgresql-
server in the default file.
Seth Vidal wrote:
I have no idea what that would do? just tell the user tough noogies?
packagename can't be downgraded because of file
Bruno Wolff III wrote:
Postgres isn't even updatable. You need to do dumps before doing
the upgrade.
OK, maybe that isn't a good example then.
However, using your comment, and turning my idea around, if
PostgreSQL isn't upgradable, according to my idea it should be
excluded by default
Seth Vidal wrote:
Seriously:
yum downgrade
and in F12 - try out things like the history undo options.
there are lots of potential nasty situations that can happen but I
think the general consensus was 'screw it, let the user sort it out
if it breaks, which it often does not'
It's Friday, so I'll allow myself to digress -
Ilyes Gouta wrote:
think that the has_gem thing is exported for X11 and Xv user-space
through a GEM ioctl property and it doesn't interfere with the rest of
Whenever I see GEM I get weird DOS GUI flashbacks, and they hurt.
Couldn't they have
Taking a step back to look at a broader picture,
what is determined here might be helpful when migrating
other packages such as :
perl6
php6
java2 ( or whatever Sunacle calls it officially )
ruby2
Although none of those are as central to the operation
of Fedora as python, they all will suffer
Adam Williamson wrote:
(My thinking is that probably there's going to be a fairly even split
between those who want to use a calendaring system from a web front
end
and those who'd prefer to use it from a desktop app, and unless we
cater
to both groups, it won't really work; for a
