Jump to content
The Dark Mod Forums

honzi

Member
  • Posts

    4
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

357 profile views
  1. I never had any problems running it without Arch packaging on my Arch system. And to make it system-wide, there's always /opt and a manual creation of /usr/share/applications/*.desktop. To me, an AUR package is always optional. And I'm not knocking your package, it's just not my thing. Also I'd just really like to submit my patch to the installer.
  2. Oh, I think you're talking about updating the buildscript, but I meant updating the updater itself. Although I'm not really sure how to submit my patch. SVN doesn't really have a pull request system.
  3. Yeah I've seen it on the AUR, but it depends on the availability of an external repo which seems a little convoluted to me. And it didn't work for me when I tried it. I'd rather have a clean install script if only for myself. Of course one can ignore the return value in PKGBUILD (which is a workaround I've been using), but aside from repo-specific packaging, having the updater return 1 on success seems a bug to me.
  4. Hey, so I was messing with the updater trying to write a pkgbuild for my Arch system and noticed that the updater always returns 1 on success. Is that behavior intended? Digging around in the updater code it seems that _outcome is never set to Ok when UpdateController goes through all the steps, so after the update is done and exitCode is determined, it falls into this thing: case ConsoleUpdater::None: // should not happen? break; Is that something you would accept a patch for?
×
×
  • Create New...