From nobody Thu Mar 28 21:48:21 2024 X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mail-it0-f53.google.com (mail-it0-f53.google.com [209.85.214.53]) by lists.alpinelinux.org (Postfix) with ESMTP id 118B85C4E1F for ; Sun, 28 Jan 2018 17:11:11 +0000 (GMT) Received: by mail-it0-f53.google.com with SMTP id u62so5634542ita.2 for ; Sun, 28 Jan 2018 09:11:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hq-adiscon-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=/k5xjSr9JMIJbVZULzET/W/J9avggeGdb+Qk27dX3sU=; b=tueLLu+ANqv9Tgih02htw8fA8Rt61QDNp+ev/wmoAQuMFpqOexAgL0oy1fKqacUc8J 8XqDNSsKTe1yuHDuw0cuJknjZhNZU3cH+vG61Z3/RU0TzGcSqW1tl/pyjGFKoctee4tZ wPfTcM/My9bQpkP2ZIDh7i7QjRzc5VSfiAcyLl18oAi1ZYSvGUoe6P5bVKNtbwJ3hnvd jK2iFQ0T3Ce/KpQMMgs4Kk6X5w1mxNPXLtaM5S7aCKSVpIMNAxOPrvlSr/F7PsOJQ+2C cRH6hcnKnukls0cr6TN8Zmu++jnd0kzouc4LviRY9uUarj5aVQBD2c7uc4fS0WHd2+Nk +SsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=/k5xjSr9JMIJbVZULzET/W/J9avggeGdb+Qk27dX3sU=; b=qeimK+ioDQl4qiDL3qZ+pBgPQ8TmphaxT6o4dFlzGZ4oAZBhAjKvX+xzMWJSrz37+r w+42MOCy8VOcRbPmpg7joIhsP8tJSMIBdQBo4P9p9eZahMt6DHT9D6UGGLMtByVw+vxw Ki8EuQ4A50sgegw1uUhRrH9Or3vjTRObbrXB8msK3sBZcD+XC22atGZt55E9Yi3ucP9m PyViJiRQ4pkGqkXri53DtOdTrBo/cf8OpmZlg4Tz2Q2+fRSuBjRq/15KTOhDoNfsM0Nw ujCvSlEEz9a3LG0csF6Ge0kcvqX63vBfQc9un2sXjWpeoivkboLa+yJNEw+3bVQJx1ZZ Vjuw== X-Gm-Message-State: AKwxytcQenKRRA3uuwYK2KMagiXmzezSGUgUuj6/U4bUzRTYrOaSDp/W RZzm5GMXKKDrdLgxAGThAVPQOnUfrD/p7PyApLRodQLz X-Google-Smtp-Source: AH8x226m+i4MPB6RKtvx3Y9YJFxRY3Ff1M3A+c8+gLrn//n6yR1CdU8Z/Qtv6m+QdcapUUWl1iM7qDkSAl9qNsAocHw= X-Received: by 10.36.33.85 with SMTP id e82mr25425385ita.135.1517159471086; Sun, 28 Jan 2018 09:11:11 -0800 (PST) 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.2.8.141 with HTTP; Sun, 28 Jan 2018 09:10:30 -0800 (PST) From: Rainer Gerhards Date: Sun, 28 Jan 2018 18:10:30 +0100 Message-ID: Subject: [alpine-devel] Version numbers for daily build packages To: alpine-devel@lists.alpinelinux.org Content-Type: text/plain; charset="UTF-8" Hi all, we (the rsyslog project) would like to build daily packages for Alpine. I have checked APK sources, but still am a bit puzzled on how we should name these versions. The idea is that a stable version should always update over an equal-target-version daily build, but new daily builds should automatically be updated. Ex: currently 8.32.0 is our stable version, 8.33.0 is being worked on. So far I found that we could use this scheme: 8.32.0 -> current stable 8.33g, e.g. 8.33d20180128 -> daily builds 8.33.0 -> next release apk --test tells me 8.32.0 < 8.33d2018... < 8.33.0 ... but I wonder if there is a better/more standard way in Alpine of doing this. Feedback is appreciated, Rainer --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org --- From nobody Thu Mar 28 21:48:21 2024 X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mail-qk0-f193.google.com (mail-qk0-f193.google.com [209.85.220.193]) by lists.alpinelinux.org (Postfix) with ESMTP id AA2B75C4E22 for ; Mon, 29 Jan 2018 16:27:53 +0000 (GMT) Received: by mail-qk0-f193.google.com with SMTP id u76so6249615qku.11 for ; Mon, 29 Jan 2018 08:27:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dereferenced-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DbBKHJPNOnJafTKRowOZ4O8j/O/ynpWLLibJkSIy0Ic=; b=dv6+Ogh7eeCfqFqT8aeDNN31tR/oek7tINkYwKe1xmzY9Y26qj+yogEvs1XDNOQYQD Y2a5bdWkloMTKcQug4+sg+qHtPeeHU/U1Mjk4vVgcUHAuw/CJ2JIt0jbXedA9oaWoGvR UR2XGOu5nMxEp6qQ3RmMOh3BYVV9S3I6hriCihdDP7ZgOgVnhs/5EHqNduCtbQkmAe6w udjbiB1kiDFNp1Wz7kSUBfvzCk4T5OI4Zv9HualE/hEz2XxdDUs5HadEDMQau49ZhJzt rSeCTEYA8QhWNzkBSwsMoB6WKGgfLZylWN4QOeoDY6+c5CzpmEEyF+Pu8a30TBiIekpj Bgzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DbBKHJPNOnJafTKRowOZ4O8j/O/ynpWLLibJkSIy0Ic=; b=EanVH25hRenCBtMZ+DjNKG4NHmpb116GxR50FGT7BKGQe12mKlmM03uoRBye3g0YkH /QvwiNxlDFgNkiQ4+HSpQYD42ANEX8tfrTUa5eZSPLeVWN5duxqkfpD6SrNu8lVN2Gi8 k4mQWyGmOwpkK9tnJfQrkhEDn7/K4bArj9ZTxr9uKtB7HOkSdOHRb0uPRpPMP+qzWxT+ T03aC7YSsTRGPjHgzsR3OjUxCziFLNNfoDicTnQcPee4cdQVK9jFmnPUMptjeibzScz+ 2BbhWZYh+7fmbWI9ojopFj5Mhpu7VBK4L+Wwmo8CA8qozs6/O9k9pU7u7Rg2fLjVdO78 78qQ== X-Gm-Message-State: AKwxytf5sT3/WaSo+pQc5AGgbEQVNmw+SdpJV0/qhlb2xUAFWhjoD5mB zOzSa4kin7wsaZJi60U9s+qDY1RB8mLBnR50tQrR2Q== X-Google-Smtp-Source: AH8x224EQfgmy3iaBypALTTQKoeZ4+Q9mjncnDPMXW0jqhBWAAW42Un6ZTnSV4MgJ056yp3BK9SqnyIjH5nLRf/Nx4U= X-Received: by 10.55.59.137 with SMTP id i131mr38252066qka.42.1517243273216; Mon, 29 Jan 2018 08:27:53 -0800 (PST) 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.200.39.100 with HTTP; Mon, 29 Jan 2018 08:27:52 -0800 (PST) In-Reply-To: References: From: William Pitcock Date: Mon, 29 Jan 2018 10:27:52 -0600 Message-ID: Subject: Re: [alpine-devel] Version numbers for daily build packages To: Rainer Gerhards Cc: alpine-dev Content-Type: text/plain; charset="UTF-8" Hello, On Sun, Jan 28, 2018 at 11:10 AM, Rainer Gerhards wrote: > Hi all, > > we (the rsyslog project) would like to build daily packages for > Alpine. I have checked APK sources, but still am a bit puzzled on how > we should name these versions. The idea is that a stable version > should always update over an equal-target-version daily build, but new > daily builds should automatically be updated. > > Ex: currently 8.32.0 is our stable version, 8.33.0 is being worked on. > So far I found that we could use this scheme: > > 8.32.0 -> current stable > 8.33g, e.g. 8.33d20180128 -> daily builds > 8.33.0 -> next release > > apk --test tells me > 8.32.0 < 8.33d2018... < 8.33.0 > > ... but I wonder if there is a better/more standard way in Alpine of doing this. The standard way would be to have 8.33_pre20180128 as the version. William --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org --- From nobody Thu Mar 28 21:48:21 2024 X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mail-it0-f46.google.com (mail-it0-f46.google.com [209.85.214.46]) by lists.alpinelinux.org (Postfix) with ESMTP id 49A0A5C4E1E for ; Mon, 29 Jan 2018 17:00:16 +0000 (GMT) Received: by mail-it0-f46.google.com with SMTP id c16so9123664itc.5 for ; Mon, 29 Jan 2018 09:00:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hq-adiscon-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=60jBZtCU+6oSPwSqolec74cgZpvpbJNgsgEuqoIby9o=; b=FJEdS0HsGcu/a9zDLlF8JlOeP2XHEjtWQFYWhxIcbvKpLOG0zvRE63J+L/jzzq6OuE hYVfRE4F8yfk1kVfzLFpjRInrBkIutrz8SYbPPz6qHXEIY5PI4pXyxiUPlismDasc6jn AsSzRe0UkMBjgRIb+5wFj1ycrzD+9EEsM+e4mj3sXrYCrHGKF08TygOlCAaLEEe3ZjKm Snl0ylHcLoi0Kd0iW3rAqYHnJvjP+egC+NacBHbrZ9eq/9RjCbAZ9hlDcFXZpeOjbDGB Vcwu6KorC8u7pUP+btlgdygF9CxoRxXC4yOsyvmRUuuOwSrZRqDRII8BaSEvRhzZYVtf /h+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=60jBZtCU+6oSPwSqolec74cgZpvpbJNgsgEuqoIby9o=; b=Auqfq7RZwyHxeAKTx58IUDJYY1Z8ihx7M4CUMSS8WM/ERnTtsdi1f+QfIceTUgbUU7 3b4WosD4u0l6Cr0IX7ptJbrYtEqypFhiGK92sV+lzte9+JSvxMilXMN8BQ2G8FXyPxXO a4rS6kSZ6FrP2u2xDHQD81hKcakQpl8QkuXw0vNpXtl0epszB5TFs3E6iOjacLyC0j1s 2DRRCbbXWYIcHYMUoHRdQ3iByrOEP+5ZySggl/4rBmpCFe2Pq35eo1dtI2DnqkIbW15e 0rttQhb0tNW3P0ZZPCKyd2o61Z74hrnl03Ym0Kz1bqXGRN1oCRzWx1yhc4wehgc/p3RT k2jg== X-Gm-Message-State: AKwxytd8/TkvCaWfW4lufsrxt53xeKgC+BFP0zXWXkunBgJPbP2pjul+ 2bdO9bq4rH1j8b8o2iQ5zKTBDlUbOysyTX5rASCvFiHA X-Google-Smtp-Source: AH8x2263BNq7Fk4YZoFBroEH0OMk0zED0Sqp36KAr1bKFNQLP+IQ58uUAVp3Hjxs/Cfh5nDhfhJtLmUQGMRW4o1gHGw= X-Received: by 10.36.14.76 with SMTP id 73mr26966759ite.43.1517245215665; Mon, 29 Jan 2018 09:00:15 -0800 (PST) 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.2.8.141 with HTTP; Mon, 29 Jan 2018 08:59:35 -0800 (PST) In-Reply-To: References: From: Rainer Gerhards Date: Mon, 29 Jan 2018 17:59:35 +0100 Message-ID: Subject: Re: [alpine-devel] Version numbers for daily build packages To: William Pitcock Cc: alpine-dev Content-Type: text/plain; charset="UTF-8" 2018-01-29 17:27 GMT+01:00 William Pitcock : > Hello, > > On Sun, Jan 28, 2018 at 11:10 AM, Rainer Gerhards > wrote: >> Hi all, >> >> we (the rsyslog project) would like to build daily packages for >> Alpine. I have checked APK sources, but still am a bit puzzled on how >> we should name these versions. The idea is that a stable version >> should always update over an equal-target-version daily build, but new >> daily builds should automatically be updated. >> >> Ex: currently 8.32.0 is our stable version, 8.33.0 is being worked on. >> So far I found that we could use this scheme: >> >> 8.32.0 -> current stable >> 8.33g, e.g. 8.33d20180128 -> daily builds >> 8.33.0 -> next release >> >> apk --test tells me >> 8.32.0 < 8.33d2018... < 8.33.0 >> >> ... but I wonder if there is a better/more standard way in Alpine of doing this. > > The standard way would be to have 8.33_pre20180128 as the version. Thanks, that was very useful. I didn't find that convention anywhere. I have now changed the version to that format. Rainer --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---