You are not logged in.

#1 2012-03-15 06:28:14

taylorchu
Member
Registered: 2010-08-09
Posts: 405

should we stick to arch principle for aur?

i faced this issue when i saw the way google-chrome-* is packed relatively non-arch way. it moves binary around, and adds unnecessary symlinks. it no longer seems simple enough to me.
https://aur.archlinux.org/packages/go/g … v/PKGBUILD

the way i packed google-chrome is that i simply unzip the rpm and copy over the directories. this looks much simpler than the first way.
https://aur.archlinux.org/packages/go/g … i/PKGBUILD

which one is better?

Last edited by taylorchu (2012-03-15 06:28:31)


"After you do enough distro research, you will choose Arch."

Offline

#2 2012-03-15 06:59:48

ngoonee
Forum Fellow
From: Between Thailand and Singapore
Registered: 2009-03-17
Posts: 7,362

Re: should we stick to arch principle for aur?

'Simple' doesn't always mean 'do less work'. If you looked at the comments you'd know why each of the changes are made. Some knowledge of FHS would be useful as well.


Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.

Offline

Board footer

Powered by FluxBB