Arch Linux User Repository

@verbote, I'm having a big of a problem getting the secondary cabextract sorted out. I can get makepkg to unpack the exe file, but it's not extracting the resulting cab file, I'm probably just missing something... if all else fails I'll remove the first one, since it does seem a little...... redundant to have makepkg extract the exe file, just to cabextract the exe file before cabextracting the cab file.. ( Say that 10 times real fast ). I'm open to suggestions, here.. on a side note, I'm down to 56 Perl Packages that are in need of updating by hand!! Unfortunately, I was very busy this weekend sorting out a gaggle of family issues for my sis-in-law and her squad, I sat down no less than 30 times to play with this, and got interrupted, sidetracked or some other form of irreversible distraction. Thx for the patience.

@ DaveCode, I said caution, not meh, if you have a suggestion then say so. Accusing Debianista is kind of gross, my caution against PKGBUILD changes does not equate to "I'm a pretentious jerkface that is too busy and/or lazy to address issues" it equates to "a lot ppl use this, if something breaks, they're going to get mad and maybe stop using this.." with the whole "don't fix what ain't broke" mentality. Yes ARCH 'has' changed alot.. I've had to go through almost 700 Perl packages bringing them up to date with pacman 4.1, I also work fulltime as a sysadmin and manage a very large family, while contributing to the Arch community a great deal, with over 700 AUR packages, an Unofficial User Repo, help in the IRC room and work locally with new Arch users to get them up to speed. so while ARCH/pacman have changed alot since this package was born, this package does still work, so if i err to caution, so be it. If you have a valuable idea to contribute, please, by all means do... But do not accuse me of 'Debianista' because of my apprehension to making changes to one of the most popular AUR packages in the system. -- jnbek Pretentious Jerkface

Voted for this package. Mod that opinion on changing PKGBUILDs. It sounds like a Debianista (as does "meh" which makes me barf). In those 6 years, Arch has changed a LOT. PKGBUILDs need to keep pace. We use Arch not Debian for a reason.

@vorbote, I will look into that, I am however rather skeptical about making too many changes to this PKGBUILD as it is and has been working very well for over 6 years. Being in the top 60 highest rated pkg out of 41000+ affords great caution with regard to PKGBUILD changes. I will however take a look at your suggestion and go from there. I appreciate your concern.

There is no need to use cabextract at all. Pacman is linked to libarchive and it will handle file extraction by itself automatically. You can use ttf-ms-fonts' PKGBUILD as an example of how this works.

You're welcome! :)

hrm, thanks @AkiraYB, perhaps i should as well :)

He probably used namcap: https://wiki.archlinux.org/index.php/Namcap

Meh, your changes didn't break anything, so I'll acquiesce to your request, however loquacious it came across ;-) In the future please be verbose about what commands were executed in order to get the reported errors for more rapid dispensation of said offense.

@coyote25, so... I'm not sure how you got those errors... care to elaborate how one goes about replicating this offensive spew?