Package Base Details: linux-ck

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only)
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 405
Popularity: 5.604703
First Submitted: 2011-07-22 14:51
Last Updated: 2019-05-16 20:56

Packages (2)

Anonymous comment on 2011-08-21 10:52

@gravsky: Thanks for your answer! I looked at the link you posted and checked the new makepkg.conf for a difference to mine. The only thing I found was that in my makepkg.con is

CARCH="x86_64"
CHOST="x86_64-unknown-linux-gnu"

and in the new one there is

CARCH="@CARCH@"
CHOST="@CHOST@"

Do I have to change mine to the new one?

Best regards and thanks for your help!

Det commented on 2011-08-21 10:03

@graysky, seems like you didn't understand the rest of my post either. What I meant was that there's no need to bump the pkgrel like that when the users should rebuild their package. It is a general rule in the AUR that when something breaks and requires a rebuild it's in the user's responsibility to rebuild the package. There's also the thing that [testing] users might've already rebuilt their package so when the maintainer bumps the pkgrel it's not really... nice.

It's of course your choice. Your package, your rules but I'd just appreciate it, if you just made a comment about something like that. In this case the rebuild wasn't even 'required'.

And the other thing was that instead of:
"-march=native -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"

it would be perfecty fine (and more accurate) to use just:
"-march=native"

I explained this in my previous post.

graysky commented on 2011-08-20 18:41

@feilen - /etc/makepkg.conf contains CFLAGS and CXXFLAGS while the PKGBUILD contains KCFLAGS and KCPPFLAGS. Makepkg will automatically set the CFLAGS and CXXFLAGS from /etc/makepkg.conf when you invoke it. It's redundant to echo them again prior to the make steps.

feilen commented on 2011-08-20 18:20

That's what I was looking at. You said in a previous post KCFLAGS and KCCPFLAGS and the PKGBUILD has KCFLAGS and KCPPFLAGS.

graysky commented on 2011-08-20 17:03

@Lothium - that's really odd. The files in question can be found here: http://projects.archlinux.org/svntogit/packages.git/tree/pacman/trunk

Anonymous comment on 2011-08-20 15:59

Mmmh... I updated to the latest pacman, but I have no makepkg.conf.pacnew... What I have to do?

graysky commented on 2011-08-20 13:52

@ethail - my bad! Bump to -4
@Det - I don't understand your question... do you feel that I'm forcing users to rebuild by bumping the PKGBUILD?

graysky commented on 2011-08-20 13:51

@ethail - my bad! Bump to -4

Det commented on 2011-08-20 12:29

Shouldn't it be the choice of individual AUR users to rebuild their manually installed packages manually themselves anyway?

E: my testing results show that the KC(PP)FLAGS are the ones set by the "Processor family" config option and they are added to the end of the gcc flag string already set by makepkg.conf. So it's unnecessary to define "-O2 -pipe" there - especially if the user has set "CONFIG_CC_OPTIMIZE_FOR_SIZE=y" (to use the '-Os' gcc flag instead of the default -O2).

Det commented on 2011-08-20 11:35

Shouldn't it be the choice of individual AUR users to rebuild their manually installed packages manually themselves anyway?