On Fri, Jul 28, 2017 at 02:20:47PM +0200, Rainer Müller wrote:
On 2017-07-28 04:06, Zero King wrote:
On Thu, Jul 27, 2017 at 07:56:27PM +0200, Clemens Lang wrote:
I would argue that the repository should in fact contain the MacPorts
source code. Ideally, without change in the repository, the bu
On 2017-07-28 04:06, Zero King wrote:
> On Thu, Jul 27, 2017 at 07:56:27PM +0200, Clemens Lang wrote:
>> I would argue that the repository should in fact contain the MacPorts
>> source code. Ideally, without change in the repository, the build
>> results should be exactly the same, so there should
Hi,
- On 28 Jul, 2017, at 04:06, Zero King l...@macports.org wrote:
> On Thu, Jul 27, 2017 at 07:56:27PM +0200, Clemens Lang wrote:
> > What's your use case for re-tagging on the same commit? I.e. what change
> > do you expect from rebuilding without changing something in the
> > repository (
Just my 2c. I would also prefer to do the necessary changes in the
same repository unless there's a valid technical reason that would
prevent us from being able to do it (like Travis not allowing us to
build/upload often enough).
In case there's a bug in base, it has to be fixed anyway.
Mojca
On Thu, Jul 27, 2017 at 07:56:27PM +0200, Clemens Lang wrote:
Hi,
On Thu, Jul 27, 2017 at 01:51:31AM +, Zero King wrote:
I prefer using a separate repository (only containing .travis.yml and
maybe patches, not MacPorts source) because I can update the binaries
by creating a new release (tag
Hi,
On Thu, Jul 27, 2017 at 01:51:31AM +, Zero King wrote:
> I prefer using a separate repository (only containing .travis.yml and
> maybe patches, not MacPorts source) because I can update the binaries
> by creating a new release (tag) on the same commit (MacPorts version
> can be read from t
On Wed, Jul 26, 2017 at 06:19:16PM +0200, Clemens Lang wrote:
Hi,
- On 25 Jul, 2017, at 17:27, Rainer Müller rai...@macports.org wrote:
On 2017-07-22 13:26, Zero King wrote:
In [1], I patched MacPorts in an attempt to fix a bug (port(1) failed
randomly on Travis). As it seems to be a Trav
On Jul 26, 2017, at 11:19, Clemens Lang wrote:
> For example, we could upload a generated archive to Bintray and update a
> file that always contains the URL to the latest archive and just download
> that in the Travis CI job.
>
If we want to use BinTray for any MacPorts things, I already regis
Hi,
- On 25 Jul, 2017, at 17:27, Rainer Müller rai...@macports.org wrote:
> On 2017-07-22 13:26, Zero King wrote:
>> In [1], I patched MacPorts in an attempt to fix a bug (port(1) failed
>> randomly on Travis). As it seems to be a Travis-specific bug, I plan to
>> use a separate repository to
On 2017-07-22 13:26, Zero King wrote:
> In [1], I patched MacPorts in an attempt to fix a bug (port(1) failed
> randomly on Travis). As it seems to be a Travis-specific bug, I plan to
> use a separate repository to generate MacPorts archives used in CI and
> keep the patch there. This way we can up
10 matches
Mail list logo
