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: 395
Popularity: 1.240394
First Submitted: 2011-07-22 14:51
Last Updated: 2019-02-16 18:54

Packages (2)

graysky commented on 2011-08-21 12:27

@Det - The main reason why I bumped it to -4 is that I need to rebuild all of the repo packages, and to make that a meaningful exercise, the pkgver needs to increase or else pacman won't pick up that something changed and trigger an update. I want to keep the AUR and repo packages "in sync" so bumping to force a rebuild is required.

To comment on your 2nd point about the long string for KCFLAGS/KCPPFLAGS: Since the KCFLAGS and KCPPFLAGS are as I understand it defined by the Makefile (or similar) included with the linux source. As I understand it, unless a user implicatively defines them at the make step, the generic defaults are used. Please correct me if I'm mistaken. Also, I do not believe that march=native provides the ARCH defaults of "-fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2" but also please correct me if I'm mistaken.

@Loth - My bad for pointing you to the pre-files. See an example of /etc/makepkg.conf here (adjust for your $arch): http://pastebin.com/YGqujRL2

Det commented on 2011-08-21 11:15

@Lothium, it seems like you just fetched makepkg.conf from the [pacman] sources, through ABS or from here: http://projects.archlinux.org/svntogit/packages.git/tree/pacman/trunk/makepkg.conf.

Either way, a simple "fix" would be to just remove your makepkg.conf and let pacman install the right one with:

# pacman -Syy pacman

E: wait, no, forget about that. It was just me not paying attention. The "@CARCH"and "@CHOST" stuff are just there to be changed in build time based on whether you are on i686 or x86_64. Nothing to worry there and definitely don't just copy+paste that file to your makepkg.conf

But if you don't have a makepkg.conf.pacnew file in /etc - that's perfectly fine. The confs are prefixed like that only when the previous file had changed since the previous update (meaning _you_ changed it).

So when you haven't changed the file in any way it can simply be replaced with the new one.

Det commented on 2011-08-21 11:04

@Lothium, it seems like you just fetched makepkg.conf from the [pacman] sources, through ABS or from here: http://projects.archlinux.org/svntogit/packages.git/tree/pacman/trunk/makepkg.conf.

Either way, a simple "fix" would be to just remove your makepkg.conf and let pacman install the right one with:

# pacman -Syy pacman

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?