[prev in list] [next in list] [prev in thread] [next in thread] 

List:       debian-user
Subject:    Re: Unable to install custom package using defined dependency version
From:       Sijis Aviles <sijis.aviles () gmail ! com>
Date:       2017-05-28 15:02:15
Message-ID: CAKVi-bJ1uLK7kLdFJpKOYRk+=Aoi89zJkgQmYPHNhd=5B=C0mA () mail ! gmail ! com
[Download RAW message or body]

On May 27, 2017 3:48 PM, "David Wright" <deblis@lionunicorn.co.uk> 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 the package name include the
> version (eg my-app-1.0.5).
>
> That's an interesting approach I didn't think about.
>
> Related, but how do other places do "nightly" build of their packages.

I don't know what they are.

I just thought about this.

I've been uploading these packages under the 'main' component name. What if
I uploaded the packages under a 'nightly-$(date)' component name instead?
In theory if I have my sources.list setup right, the my-app and app-configs
would need to change their package name to include the version. It would
also mean that they only find each other, right?

I haven't tested this theory out.

Sijis

[Attachment #3 (text/html)]

<div dir="auto"><div><br><div class="gmail_extra"><br><div class="gmail_quote">On May \
27, 2017 3:48 PM, &quot;David Wright&quot; &lt;<a \
href="mailto:deblis@lionunicorn.co.uk">deblis@lionunicorn.co.uk</a>&gt; wrote:<br \
type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex">On Sat 27 May 2017 at 13:51:01 (-0500), Sijis Aviles \
wrote:<br> <div class="quoted-text">&gt; On May 26, 2017 7:09 PM, I wrote:<br>
&gt;<br>
&gt;&gt; cpp-4.8 and gcc-4.8,<br>
&gt;&gt; python2.7-minimal and python2.7,<br>
&gt;&gt; python3-minimal and python3,<br>
&gt;&gt; etc.<br>
&gt;&gt;<br>
</div><div class="quoted-text">&gt;   Ahh, I didn&#39;t realize you suggested to make \
the package name include the<br> &gt; version (eg my-app-1.0.5).<br>
&gt;<br>
&gt; That&#39;s an interesting approach I didn&#39;t think about.<br>
&gt;<br>
&gt; Related, but how do other places do &quot;nightly&quot; build of their \
packages.<br> <br>
</div>I don&#39;t know what they are.<br>
<br>
</blockquote></div>I just thought about this.</div></div><div class="gmail_extra" \
dir="auto"><br></div><div class="gmail_extra" dir="auto">I&#39;ve been uploading \
these packages under the &#39;main&#39; component name. What if I uploaded the \
packages under a &#39;nightly-$(date)&#39; component name instead? In theory if I \
have my sources.list setup right, the my-app and app-configs would need to change \
their package name to include the version. It would also mean that they only find \
each other, right?</div><div class="gmail_extra" dir="auto"><br></div><div \
class="gmail_extra" dir="auto">I haven&#39;t tested this theory out.</div><div \
class="gmail_extra" dir="auto"><br></div><div class="gmail_extra" \
dir="auto">Sijis</div></div>



[prev in list] [next in list] [prev in thread] [next in thread]