On May 27, 2017 3:48 PM, "David Wright" wrote:
On Sat 27 May 2017 at 13:51:01 (-0500), Sijis Aviles wrote:
> On May 26, 2017 7:09 PM, I wrote:
>
>> cpp-4.8 and gcc-4.8,
>> python2.7-minimal and python2.7,
>> python3-minimal and python3,
>> etc.
>>
> Ahh, I didn't realize you suggested to make th
On Sat 27 May 2017 at 13:51:01 (-0500), Sijis Aviles wrote:
> On May 26, 2017 7:09 PM, I wrote:
>
>> cpp-4.8 and gcc-4.8,
>> python2.7-minimal and python2.7,
>> python3-minimal and python3,
>> etc.
>>
> Ahh, I didn't realize you suggested to make the package name include the
> version (eg my-app
On May 26, 2017 7:09 PM, "David Wright"
No, you will type:
$ apt-get install my-app-1.0.5 and it will install app-configs-1.0.5,
$ apt-get install my-app-1.0.6 and it will install app-configs-1.0.6.
Yes, you reported that. That's because you've made it depend on
"package app-configs version 1.
On Fri 26 May 2017 at 13:26:54 (-0500), Sijis Aviles wrote:
> On Fri, May 26, 2017 at 12:42 PM, David Wright
> wrote:
>
> > Why not just copy the x.y.x version into the package name,
> > and then add 1 to allow for updates/corrections. That way,
> > you can even have both versions coexist.
> >
>
On Fri, May 26, 2017 at 12:42 PM, David Wright
wrote:
> Why not just copy the x.y.x version into the package name,
> and then add 1 to allow for updates/corrections. That way,
> you can even have both versions coexist.
>
> app-configs-1.0.5 1.0.5-1
> app-configs-1.0.6 1.0.6-1
>
> à la
On Fri 26 May 2017 at 10:02:20 (-0500), Sijis Aviles wrote:
> On Fri, May 26, 2017 at 9:16 AM, Frank wrote:
> >> If I understand what you say, only 1 version of app-configs should
> >> be available in the debian repo in order for this to work.
> > Simply put: in any particular repository the most
On Fri, May 26, 2017 at 9:16 AM, Frank wrote:
>> If I understand what you say, only 1 version of app-configs should
>> be available in the debian repo in order for this to work.
>>
>
> Simply put: in any particular repository the most recent version of the
> dependency should be compatible with
Op 26-05-17 om 14:52 schreef Sijis Aviles:
As suggested, I was able to tell apt to install the specific
1.0.5~aaa package first and then I was able to install 'my-app' in a
subsequent command. This works but its not what I was expecting to
do.
What I was trying to do was automatically build '
Frank,
On Fri, May 26, 2017 at 6:54 AM, Frank wrote:
> Op 25-05-17 om 23:36 schreef Sijis Aviles:
>
>> It seems that my qualifier of '=' isn't working as I expect. What am I
>> doing
>> wrong?
>>
>
> You appear to assume you can tell apt to ignore a newer version of one
> package by specifying a
Op 25-05-17 om 23:36 schreef Sijis Aviles:
It seems that my qualifier of '=' isn't working as I expect. What am I doing
wrong?
You appear to assume you can tell apt to ignore a newer version of one
package by specifying a previous version of that package as a dependency
of another package. Yo
10 matches
Mail list logo
