You are not logged in.

#1 2009-11-24 20:16:56

dcc24
Member
Registered: 2009-10-31
Posts: 732

Mono No No!

After seeing this I've made an Arch package working with the same principle.

Basically it's a dummy package that simply "conflicts with mono". If some package tries to install mono as a dependency, the conflict will grab your attention. It also creates a dummy "/usr/bin/mono" which warns you that mono is disabled by the mononono package.

Why? I don't like the idea behind Mono. Let's not discuss the issue, there are already enough flame wars on this. Use it if you like it.


It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)

My AUR packages

Offline

#2 2009-11-24 21:14:08

hBd
Member
From: Romania - Cluj Napoca
Registered: 2008-06-08
Posts: 241
Website

Re: Mono No No!

lol?

Offline

#3 2009-11-24 21:16:57

dcc24
Member
Registered: 2009-10-31
Posts: 732

Re: Mono No No!


It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)

My AUR packages

Offline

#4 2009-11-24 22:38:42

Nezmer
Member
Registered: 2008-10-24
Posts: 559
Website

Re: Mono No No!

You shouldn't touch "/usr/bin/mono" in the ".install" file. That means It's not owned by any package. Do It in build()


English is not my native language .

Offline

#5 2009-11-24 22:44:36

dcc24
Member
Registered: 2009-10-31
Posts: 732

Re: Mono No No!

How? If I place it in build() it'll complain that it can't write in /usr/bin since build is done with a non-root user. How should I do it?


It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)

My AUR packages

Offline

#6 2009-11-24 23:01:48

Arm-the-Homeless
Member
Registered: 2008-12-22
Posts: 273

Re: Mono No No!

dcc24 wrote:

How? If I place it in build() it'll complain that it can't write in /usr/bin since build is done with a non-root user. How should I do it?

touch $pkgdir/usr/bin/mono

Offline

#7 2009-11-24 23:05:47

dcc24
Member
Registered: 2009-10-31
Posts: 732

Re: Mono No No!

Doesn't make a difference. During makepkg:

touch: cannot touch `/usr/bin/mono': Permission denied

It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)

My AUR packages

Offline

#8 2009-11-24 23:06:25

Xyne
Administrator/PM
Registered: 2008-08-03
Posts: 6,963
Website

Re: Mono No No!

The very idea of creating a dummy package just to conflict with another package is bad enough and would have merited deletion on its own.
The fact that it completely disregarded all packaging standards just abbreviated my hesitation.

Here are some relevant links for future reference:
http://wiki.archlinux.org/index.php/Arc … _Standards
http://wiki.archlinux.org/index.php/PKGBUILD


Please do not upload such a package again.


*edit*

dcc24 wrote:

Doesn't make a difference. During makepkg:

touch: cannot touch `/usr/bin/mono': Permission denied

Read about packaging. In this case the build function would have been:

build()
{
  touch mono
  install -Dm644 $pkg/usr/bin/mono
}


Again though, don't do that.

Last edited by Xyne (2009-11-24 23:11:13)


My Arch Linux StuffForum EtiquetteCommunity Ethos - Arch is not for everyone

Offline

#9 2009-11-24 23:11:36

dcc24
Member
Registered: 2009-10-31
Posts: 732

Re: Mono No No!

Sure. Still, what's the correct way of "touch /usr/bin/mono" ?

I see your edit now, thanks.

Last edited by dcc24 (2009-11-24 23:12:00)


It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)

My AUR packages

Offline

#10 2009-11-24 23:23:51

foutrelis
Developer
From: Athens, Greece
Registered: 2008-07-28
Posts: 705
Website

Re: Mono No No!

I'm tempted to upload a package called monoyesyes that will conflict with mononono. tongue

On a more serious note, if you want to make sure mono doesn't get installed, you can put it in IgnorePkg in /etc/pacman.conf. With that in place, if you go to install an application that depends on mono, you'll receive the following error:

[foutrelis@failboat ~]$ sudo pacman -S gbrainy
resolving dependencies...
warning: ignoring package mono-2.4.2.3-1
warning: cannot resolve "mono>=2.4.2", a dependency of "mono-addins"
:: the following package(s) cannot be upgraded due to unresolvable dependencies:
      gbrainy

Offline

#11 2009-11-24 23:25:04

dcc24
Member
Registered: 2009-10-31
Posts: 732

Re: Mono No No!

Yeah, that does seem to be a more elegeant solution. Thanks!


It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)

My AUR packages

Offline

#12 2009-11-25 01:46:36

Wintervenom
Member
Registered: 2008-08-20
Posts: 1,011

Re: Mono No No!

This seems fruitless.  Pacman already does a commendable job of informing users when a package relies or wants to install a dependency they do not want, and is even nice enough to ask for a confirmation by default.

Last edited by Wintervenom (2009-11-25 01:50:40)

Offline

#13 2009-11-29 00:48:42

cactus
Taco Eater
From: t͈̫̹ͨa͖͕͎̱͈ͨ͆ć̥̖̝o̫̫̼s͈̭̱̞͍̃!̰
Registered: 2004-05-25
Posts: 4,622
Website

Re: Mono No No!

pacman. Fruit.
The orange was 500 points, as I recall.


"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍

Offline

#14 2009-11-30 01:22:32

Wintervenom
Member
Registered: 2008-08-20
Posts: 1,011

Re: Mono No No!

I stand corrected.  lol

Last edited by Wintervenom (2009-11-30 01:22:50)

Offline

Board footer

Powered by FluxBB