On Wednesday 22 August 2012 02:55:47 korgman wrote:
> On 21/08/2012 11:33 μμ, xgiz...@slackbuilds.org wrote:
> > I will also take this time to remind all maintainers that it is
> > very important that updates be based off of our git and not local
> > copies.
>
> I made a local copy with rsync 2 da
2012/8/22 korgman :
> On 21/08/2012 11:33 μμ, xgiz...@slackbuilds.org wrote:
>>
>> I will also take this time to remind all maintainers that it is
>> very important that updates be based off of our git and not local
>> copies.
>
>
> I made a local copy with rsync 2 days ago, is still valid or a nee
On Wed, 2012-08-22 at 09:18:45 +1000, Christoph Willing wrote:
> I have a use case where such information is actually useful rather
> than superfluous. I run each build inside an LXC container which is
> created just for that build. Rather than being a fully loaded
> Slackware system, the container
On 21/08/2012 11:33 μμ, xgiz...@slackbuilds.org wrote:
I will also take this time to remind all maintainers that it is
very important that updates be based off of our git and not local
copies.
I made a local copy with rsync 2 days ago, is still valid or a need a git local
copy?
--
Michales Mi
On Wed, 22 Aug 2012 09:18:45 +1000
Christoph Willing wrote:
>
> On 22/08/2012, at 6:33 AM,
> > wrote:
> [snip]
> >
> > Remember that in between releases master is our work in progress
> > branch and should not be considered stable or final. We will
> > summarize changes and new policies when
On 22/08/2012, at 6:33 AM, > wrote:
[snip]
Remember that in between releases master is our work in progress
branch and should not be considered stable or final. We will
summarize changes and new policies when the 14.0 branch is closer
to a usable state.
At the moment, template.info contain
On Tue, Aug 21, 2012 at 04:33:49PM -0400, xgiz...@slackbuilds.org wrote:
> On Tuesday 21 August 2012 12:55:57 Mikko Varri wrote:
> >
> > It seems that the REQUIRES field contains a full list of direct and
> > indirect dependencies, optional and suggested packages, and then some.
> > And those in A
On Tuesday 21 August 2012 12:55:57 Mikko Varri wrote:
> Hello,
>
>
> Now that REQUIRES field reached master branch, and there seems to be
> updates going in where the dependency list is being removed from
> READMEs: would it make sense to write a little summary about it?
>
> It seems that the RE
Hello,
Now that REQUIRES field reached master branch, and there seems to be
updates going in where the dependency list is being removed from
READMEs: would it make sense to write a little summary about it?
It seems that the REQUIRES field contains a full list of direct and
indirect dependencies,