X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by lists.alpinelinux.org (Postfix) with ESMTP id 5E6FE3617A22 for ; Wed, 19 May 2010 07:00:11 +0000 (UTC) Received: by fxm4 with SMTP id 4so607905fxm.13 for ; Wed, 19 May 2010 00:00:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=Q0iUwh3zT4HgbaZKtzZ/NA6hlc2+OntMUVhXEoYnzdQ=; b=UX33mJRp/9zCmbbXV8BvBUUW9K4P3JzhQT91qC3/v7w25si3qRulWFLRRl8rNs1VFz a68Zv4nijlgg7XOgc5fTWDx6qNU/fZrhAGq+798+uvcjX7ExZzW8CEhnF6wHVbjgxF7w ZSYFpNBcxxghdQCxFvlhH9FSL+imQuOJ5Rl7s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=jz7wPeznQnkI7Ox0PSWLYbfze9BouzGLvUIZAUFEZqz2jQzXTz9ipz507SOtPxgEkn i6eqjAFQ46CKNmSGS3pDeKmTZmuRZgRUmlkdBXgmhhupUzPjEYIQBOYLxBrXf10WG5xV 0NfZnKpcaTOk0ncvjf1eJeict/46FJ4VVnAGc= X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Received: by 10.102.15.22 with SMTP id 22mr5727398muo.7.1274252407960; Wed, 19 May 2010 00:00:07 -0700 (PDT) Received: by 10.204.55.4 with HTTP; Wed, 19 May 2010 00:00:07 -0700 (PDT) In-Reply-To: <4BF37448.1080901@nothome.org> References: <4BF37448.1080901@nothome.org> Date: Wed, 19 May 2010 09:00:07 +0200 Message-ID: Subject: Re: [alpine-devel] apk info --triggers From: Natanael Copa To: Nathan Angelacos Cc: Alpine-devel Content-Type: text/plain; charset=ISO-8859-1 On Wed, May 19, 2010 at 7:16 AM, Nathan Angelacos wrote: > What are apk --triggers? Triggers are a feature in apk-tools. You can in a package say: when anything changes in directory $d execute this script. For example, busybox modprobe monitors /lib/modules/*, when there is a change in there, 3rd party module or a kernel is installed or removed, the trigger script will be executed and can do a depmod. Rather than running depmod as a post-install script, once for every affected package, it is run after all packages are installed, once. Other usecase is font-cache. For each installed font the font cache needs to be updated. This is pretty slow, so if you install many fonts you win pretty much on updating the font cache once, after all fonts are installed, rather than updating font cache for each installed font. Hope that explains. -- Natanael Copa --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---