From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Wed, 08 Mar 2023 19:06:26 +0100 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pZyBF-00DrcR-4E for lore@lore.pengutronix.de; Wed, 08 Mar 2023 19:06:26 +0100 Received: from localhost ([127.0.0.1] helo=metis.ext.pengutronix.de) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1pZyBF-0002D0-6v; Wed, 08 Mar 2023 19:06:25 +0100 Received: from mail-yw1-x1129.google.com ([2607:f8b0:4864:20::1129]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pZyAy-0002C1-00 for ptxdist@pengutronix.de; Wed, 08 Mar 2023 19:06:08 +0100 Received: by mail-yw1-x1129.google.com with SMTP id 00721157ae682-536af432ee5so320264507b3.0 for ; Wed, 08 Mar 2023 10:06:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678298766; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=QwtzUtHHdxthk1lFMOSJMiTSntoiOv0JtoGSSAEOj1k=; b=EEEXRg/8lz7QraKKgJ2N59fFk5V5h5/nx+OR/SwQOEo0PSjbPUfzUa2N7ovi97nytd J1KMKS4D8a/G0Gp0n0mmrG5NGNPtUwJU6hz6rdJhIHJkoPn/rLxy1sFS1fVUdxvZ6crT GepCLgwuqGPniZ76FqLtkNs6o0I0D/DMikRh9FgHA/5tQm6kXfbH7rWwhq13iWAymtEp HhdMDc3TOqGtxPaAXXviy9oNi7bs44c1z8VeC+JUFu6fbdpEdumcBcfhnubmGs1lZqEN MnRlZg9G3TegfH4wHSyn6JSrGTxK75KO6Oafbq2Aj8Us2+K9SgjT6PC2/4QwsS1foPSp ZCVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678298766; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=QwtzUtHHdxthk1lFMOSJMiTSntoiOv0JtoGSSAEOj1k=; b=KslNc2C8g0r9DXld2Xn0tBTKdsye+XU1i8eXR7m+gQjd0Ug3Q14OEtBYpbh6yHCkf8 dKWaeTURHmLRD2k5x8sObuQSfKebyeiJ2Xrif59VVyogYEl4yWhagmznzNq0OB0JNBGs VP4+X+btuwDA9YJUDPl6uRRCjpDlb43eL/B+/tW23BeNgBx94CAuP3ZLMwkyrUc2PIF4 gN0tsmi5g8vW0X51oPbYcuLcxFRcQc5n7oCA7Ay6PcCgOYkPSrFxqmNY9rfiqfk7Cy2o LAdUqkZBEVrkOeyfYX4s6K2yV+Ay3TxkSob58dTYiSH5Fmyzo/jb4hwupetTRBiL+isq i1Ew== X-Gm-Message-State: AO0yUKWTQ1ok+B8eqpj24HNlKty8mKcdem78kYaupQdCc0TJh7XDhNQX 5F6WpOSmdjb4CcqnOF4BrVUZAEitdf4re9IcJzqvBleB2ps= X-Google-Smtp-Source: AK7set+a7JWnQBtoomzfahWaIbOnbrTGL1KDPssa9HT2F502YdzNppdf4Bw9JupmWVlI7J/X7bQp7adPlD9BFB4Kc24= X-Received: by 2002:a81:ad46:0:b0:52e:cea7:f6e0 with SMTP id l6-20020a81ad46000000b0052ecea7f6e0mr11724424ywk.7.1678298766267; Wed, 08 Mar 2023 10:06:06 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Guillermo Rodriguez Garcia Date: Wed, 8 Mar 2023 19:05:55 +0100 Message-ID: To: ptxdist@pengutronix.de, christian.melki@t2data.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.ext.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-102.8 required=4.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,USER_IN_WELCOMELIST, USER_IN_WHITELIST autolearn=ham autolearn_force=no version=3.4.2 Subject: Re: [ptxdist] Image package creating several files X-BeenThere: ptxdist@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Sender: "ptxdist" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: ptxdist-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false Hi Christian, El mi=C3=A9, 8 mar 2023 a las 18:49, Christian Melki () escribi=C3=B3: > > Hi. > > On 3/8/23 16:56, Guillermo Rodriguez Garcia wrote: > > Hello all, > > > > I have created an image package that signs some files. > > This package creates two separate files. > > > > What is the recommended way to handle this? From the documentation > > (https://www.ptxdist.org/doc/ref_make_variables.html#image-packages), > > I believe that _IMAGE is expected to contain the filename of one > > single file. For example the "clean" target uses this to know which > > file to delete. > > > > How can this be adapted for cases where more than one file is generated= ? > > > > Not sure what you mean by _IMAGE. But iirc, > barebox (etc) image installing packages handle this. > The rules can install multiple files into image directories and are > capable of cleaning up after themselves. Yes but that is a "regular" package. I am referring to "image packages", which are a bit different; see the documentation here: https://www.ptxdist.org/doc/ref_make_variables.html#image-packages In these packages, the _IMAGE variable points to a file (the image that is created by the rule). The clean target is automatically generated based on this variable. My question is how to do this if the package generates more than one image. BR, Guillermo Rodriguez Garcia guille.rodriguez@gmail.com