On 11 February 2015 at 03:39, Oon-Ee Ng wrote:
> Wasn't there a guideline somewhere against this? Should I raise bugs
> when I see this is taking place?
>
> Specific example that I just noticed is mpd, because libnfs in
> community updated. Of course, mpd was updated within 12 hours or so,
> and I
On 11 February 2015 at 09:39, Oon-Ee Ng wrote:
> Wasn't there a guideline somewhere against this? Should I raise bugs
> when I see this is taking place?
>
> Specific example that I just noticed is mpd, because libnfs in
> community updated. Of course, mpd was updated within 12 hours or so,
> and I
We are talking about runtime dependencies here, not build or test. core/
should be selfcontained, packages in core/ only depend on other core/
packages. All packages can depend on /core since its considered mandatory.
Hence the name, you can run arch with just this repo. extra/ is maintained
by arc
On 02/12/2015 03:46 AM, Genes Lists wrote:
Just FYI in case anyone else gets flaky behaviour. Be interesting to
know for those that said 'n' to the import - if they got asked a second
time or not.
Yes, you get asked a second time.
Manuel
On Thu, Feb 12, 2015 at 9:48 PM, Marko Hauptvogel
wrote:
> There is afaik no
> rule that prevents /extra packages from depending on /community, but the
> number should be kept small.
As long as there is no rule (and don't get me wrong, I'm not in favour
of unnecessary bureaucracy) then there's no
On Fri, 13 Feb 2015 10:31:44 +0800
Oon-Ee Ng wrote:
> On Thu, Feb 12, 2015 at 9:48 PM, Marko Hauptvogel
> wrote:
> > There is afaik no
> > rule that prevents /extra packages from depending on /community,
> > but the number should be kept small.
>
> As long as there is no rule (and don't get me
6 matches
Mail list logo
