Reply to topic

Muon Package Manager

raddison
Registered Member
Posts
513
Karma
0

Re: Muon Package Manager

Sun Jun 25, 2017 10:36 pm
@Ubulindy Okay, Have you seen my recently posted issues?

viewtopic.php?f=309&t=140861
viewtopic.php?f=309&t=140860
viewtopic.php?f=309&t=140794
viewtopic.php?f=309&t=140799

Not 4 but 5 issues if you check attentively (one of five is the gap at the right - now on a wish list). Tell me your opinion, like:
1. ...
2. ...

so forth

Edit: Comment on those, please.


Proud to be powered by Plasma
raddison
Registered Member
Posts
513
Karma
0

Re: Muon Package Manager

Sun Jun 25, 2017 11:08 pm
No need for a rush. First think them over. Whenever something doesn't work/behave properly, it hurts. Cause it's my favorite desktop bar none and it's my favorite OS (Neon) bar none.


Proud to be powered by Plasma
User avatar dequire
Registered Member
Posts
81
Karma
0
OS

Re: Muon Package Manager

Tue Jun 27, 2017 5:15 pm
Muon search is fixed now in Neon :)
Ubulindy
Registered Member
Posts
41
Karma
0

Re: Muon Package Manager

Tue Jun 27, 2017 6:14 pm
Weeeeee!!! \o/ You're right! :D
raddison
Registered Member
Posts
513
Karma
0

Re: Muon Package Manager

Wed Jun 28, 2017 7:35 pm
dequire wrote:Muon search is fixed now in Neon :)



Haven't checked yet but if it's fixed then I am very HAPPY. :) Weeeee!


Proud to be powered by Plasma
raddison
Registered Member
Posts
513
Karma
0

Re: Muon Package Manager

Sun Jul 16, 2017 11:46 am
I have not yet found any Muon in Discover on my Neon User LTS installs.

So I just used "sudo apt install muon" and it got installed.

The strange part is: if I go to Discover (aka the elephant in the room), I cannot see it (in Discover) as installed.

My question: what repo did I pull in Muon from? (wasn't attentive during install).

Yet another thing: while K3B appears in Discover, it is an old(er) version. 2010 to be exact. My guess is: while K3B is under active development (see GitHub or other Plasma-based distros), it is not a Neon package.

Good or bad, here's my arguable conclusion: If one is on Neon User LTS, those two (Muon and K3B) are not available in Neon's LTS repo, and are installable from Ubuntu (without modifying default source settings).

What do you think @claydoh @acheronuk @NoName?

I think Apt is the cleanest method for managing packages on Neon.

PS: To anyone: I'd like to keep the discussions on-track, if possible.


Proud to be powered by Plasma
NoNameNoBlame
Karma
0

Re: Muon Package Manager

Sun Jul 16, 2017 4:52 pm
My personal preferences are like this:

1) Updating:
Updating of packages already present with 'discover'.
Why? Because it's seemingly the tool getting the most
attention by the 'KDE Neon' maintainers.

2) Installing:
I always use command line tools.
I do my package searches with 'aptitude'.
And my installations I do with 'apt' (not 'apt-get').
This gives me the largest amount of details
and the best way to check in advance what will
happen during install or what went wrong after
a faulty install.

3) Result:
This way I satisfy the expectations of the 'KDE Neon' maintainers,
and keep maximum control over what I do and especially over
mistakes possibly made by myself.

4) Mixed using of multiple Graphical Package Managers:

The more of them one uses, the greater the attack surface gets:
For Developer or User errors.

I can't keep up with each and every Graphical UI. Therefore, I
strive to concentrate on the underlying command line tools.

They are always the same. This leads to less work, better understanding,
and more clarity when reporting bugs in package management.
raddison
Registered Member
Posts
513
Karma
0

Re: Muon Package Manager  Topic is solved

Sun Jul 16, 2017 5:59 pm
NoNameNoBlame wrote:My personal preferences are like this:

1) Updating:
Updating of packages already present with 'discover'.
Why? Because it's seemingly the tool getting the most
attention by the 'KDE Neon' maintainers.

2) Installing:
I always use command line tools.
I do my package searches with 'aptitude'.
And my installations I do with 'apt' (not 'apt-get').
This gives me the largest amount of details
and the best way to check in advance what will
happen during install or what went wrong after
a faulty install.

3) Result:
This way I satisfy the expectations of the 'KDE Neon' maintainers,
and keep maximum control over what I do and especially over
mistakes possibly made by myself.

4) Mixed using of multiple Graphical Package Managers:

The more of them one uses, the greater the attack surface gets:
For Developer or User errors.

I can't keep up with each and every Graphical UI. Therefore, I
strive to concentrate on the underlying command line tools.

They are always the same. This leads to less work, better understanding,
and more clarity when reporting bugs in package management.


@NoName Thank you. I don't like/agree to mixed package management either (4). So far, Discover does not do a great job, Muon does a fairly decent job, Synaptic is somewhat better than Muon, CLI seems to do the best job.

I wish Discover got better because it's nice and kudos for the concept but it cannot handle everything just yet. It has come a long way though.


Proud to be powered by Plasma

 
Reply to topic

Bookmarks



Who is online

Registered users: Baidu [Spider], bartoloni, Belliric, Bing [Bot], Google [Bot], jmacleod, Kresimir, Majestic-12 [Bot]