On Thu, Oct 03, 2013 at 11:54:55AM +0200, Vincent Danjean wrote:
>
> The current proposal about Depends/Conflicts/Provides is the following:
> ICD Loader:
> ===
> Section: libs
> Multi-Arch: same
> Architecture: any
> Provides: libopencl1
> Conflicts: libopencl1
> Replaces: libopencl1
> Su
Package: wnpp
Severity: wishlist
Owner: Andrew Ross
* Package name: javax.persistence
Version : 2.1.0.v201304241213
Upstream Author : Sun Microsystems, Oracle Corporation
* URL : http://www.eclipse.org/eclipselink
* License : Eclipse Public License v1.0 and Ecl
On Fri, Oct 04, 2013 at 01:31:35PM +0200, Vincent Lefevre wrote:
> On 2013-10-02 17:50:40 +0200, Dominik George wrote:
> > That said, what's the point in NOT being verbose?
>
> Version strings need to be displayed, and if they take too much space,
> they may be truncated (e.g. in aptitude).
They
Hello,
On 04/10/13 13:50, Vincent Lefevre wrote:
> On 2013-10-04 13:40:29 +0200, Dominik George wrote:
>> My argument for keeping the VCS hash is to ease identifying the code
>> in the package.
>
> Does it need to be in the version string?
> Why not somewhere else?
>
> The goal of the Version fi
Package: wnpp
Severity: wishlist
Owner: Xavier Guimard
* Package name: libnet-facebook-oauth2-perl
Version : 0.07
Upstream Author : Mahmoud A. Mehyar
* URL : https://metacpan.org/release/Net-Facebook-Oauth2
* License : Artistic or GPL-1+
Programming Lang: Pe
Le 03/10/2013 13:04, David Kalnischkies a écrit :
> On Thu, Oct 3, 2013 at 11:54 AM, Vincent Danjean wrote:
>> I tried several variation, adding :same and/or :i386/:amd64 to
>> the Conflicts and/or Provides in ICD Loader. I do not succeed into
>
> :same doesn't exist (in this context), where di
On 2013-10-04 13:40:29 +0200, Dominik George wrote:
> My argument for keeping the VCS hash is to ease identifying the code
> in the package.
Does it need to be in the version string?
Why not somewhere else?
The goal of the Version field in Debian packages is to identify
and sort several versions
Le 03/10/2013 13:28, Simon McVittie a écrit :
> On 03/10/13 10:54, Vincent Danjean wrote:
>> The only "problem" is that it is not currently possible to install
>> an ICD Loader:i386 from one vendor and an ICD Loader:amd64 from another
>> vendor.
>
> Is there a valid reason to do that, other than
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Vincent Lefevre schrieb:
>Then, do you mean that VCS hashes are sortable?
Of course not. One would have to do something like 0~MMDDnn+git in that
rare case.
My argument for keeping the VCS hash is to ease identifying the code in the
pac
On 2013-10-02 17:50:40 +0200, Dominik George wrote:
> I established an advantage for the user using my proposal - go get
> me a disadvantage for the packager.
As a user, I dislike long version strings.
> That said, what's the point in NOT being verbose?
Version strings need to be displayed, and
On 2013-10-02 16:51:09 +0200, Dominik George wrote:
> Dominique Dumont schrieb:
> >well, you proposed a version like 'hg'. if upstream switches to
> >git, you can't use a version like 'git' because it sorts before
> >hg. I grant you that is easy to work around.
>
> If you deem it unlikely
On Thu, 2013-10-03 at 13:56 -0700, Don Armstrong wrote:
> On Thu, 03 Oct 2013, Guillem Jover wrote:
> > On Wed, 2013-10-02 at 10:11:58 -0700, Don Armstrong wrote:
> > > If you do this, I'd also suggest dropping in a rule for
> > > http://bugs.debian.org/libravatar, as I will eventually be moving t
12 matches
Mail list logo
