It would seem part of the suggestion could be solved by allowing the
priority to be set in a .repo file and make that the suggested path
for adding packman (in wiki and elsewhere).
ie a file like
http://download.opensuse.org/repositories/home:/boombatower:/openage/openSU…
[home_boombatower_openage]
name=openage (openSUSE_Tumbleweed)
type=rpm-md
baseurl=http://download.opensuse.org/repositories/home:/boombatower:/openag…
gpgcheck=1
gpgkey=http://download.opensuse.org/repositories/home:/boombatower:/openage…
enabled=1
<<priority=90>> <-- add this
Perhaps it is already supported? If so then simply suggesting on
packman list to provide such a file with configured priority. The docs
could also be updated to include the highly recommended zypper dup
--from packman once step.
Also would be nifty if that priority could be altered on any OBS
repository so project maintainers can set a priority that makes sense
as described in the other thread. (perhaps already available?)
Another slick addition would be to add a --priority option to `zypper
ar` so it could be documented with priority instead of requiring an
`mr` step to change it after adding. I would actually be interested in
seeing if I could tackle adding such a feature. Note my packman setup
instructions on
https://github.com/jp9000/obs-studio/wiki/Install-Instructions which
include this longer set of steps (screenshot for lazy:
http://i.imgur.com/3L5lPE8.png).
Assuming a properly configured system I would imagine the last issue
regarding conflict resolution would be less of an issue since
conflicts should arise less often, but yast or zypper have an
interactive way to solve that. Obviously it's not automatic, but
computers cannot think quite yet.
--
Jimmy
On Tue, Jul 14, 2015 at 1:34 PM, Roman Bysh <rbtc1(a)rogers.com> wrote:
On 07/14/2015 07:42 AM, yac wrote:
On Tue, 14 Jul 2015 13:08:45 +0200
"Carlos E. R." <carlos.e.r(a)opensuse.org> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 2015-07-14 11:25, Thomas Langkamp wrote:
- automatically update/grade the OS daily: by
executing zypper up
or dup in the background (via cron-job or graphical utility?) AFAIK
apper still cannot propose solutions for conflicts and thus might
not be feasible for this job.
Never automatically.
Why not for the average
joe user?
Windows been doing this a long time.
Windows is not Linux. Linux is not Windows.
Linux is always looking at security.
One thing I've learned over time when I was a noob was that
you make it a habit of understanding how your system works.
You run through a checklist in your mind so that you know
what is being installed and what is being updated.
Security should always be on your mind.
Running an auto-update bypasses security.
Cheers!
Roman
ICQ: 551368250
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org