From: "V.Krishn" <vkrishn4@gmail.com>
Reply-To: vkrishn4@gmail.com
To: Timo Teras <timo.teras@iki.fi>
Subject: Re: [alpine-devel] Questions about apk CMD -U
Date: Sun, 25 Nov 2012 14:25:18 +0530
User-Agent: KMail/1.13.7 (Linux/3.3.7-64; KDE/4.7.4; x86_64; ; )
References: <20121029181737.GB16841@vaio.jimpryor.net> <201210301738.57593.vkrishn4@gmail.com> <20121030142314.742ff63f@vostro>
In-Reply-To: <20121030142314.742ff63f@vostro>
Cc: alpine-devel@lists.alpinelinux.org
Precedence: list
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201211251425.18336.vkrishn4@gmail.com>


> 
> I do not see point in allowing any random strings, as we could not
> really make good separation on them. And suffixing the "_myX"
> before "-rN" confuses as it would be sorted in non-logical order.
> 

Any further thought on - foo-1.2.3-r2.1-my3 ?

> I wonder if we want some package "flavor" string added to the package
> name which does not affect version sorting, but would just have
> informative purpose. I would prefer not - and just make people learn
> the repository pinning.
> 

I was wanting to release few experimental packages.
The @ method seems to be more useful in identiying one repository from 
another. What I would like is a effective means to identify custom packages 
from another.

eg. foo-1.2.3-r2.1-my3 seems to solve this.

> In general - it seems we should be going more for "packages come from
> certain repository" and sort them accordingly, even if it means
> downgrading -- instead of "try to figure out universal versioning
> scheme for package so that include also the builder info etc". The fact
> is that packages alone do not work - their dependencies must come from
> same place too.
> 

Using @ method could possibly be an issue in an automated upgrade system.

> I'm actually getting tempted to ignore the package version altogether
> in the package (store it for display only) -- and just store the
> repository commit date in the package and use it as the version test.

What happens in an event the packages get corrupted and packager rebuilds 
personal repo without incrementing _rN?

> And then have some way to specify what is the preferred order of
> repositories. This would make things a lot easier - and allow easy
> downgrading in case some package needs to be downgraded (without stupid
> hacks like Debian epoch version notation).
> 
> - Timo

-- 
Regards.
V.Krishn


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---