[EMAIL PROTECTED] writes:
> If you know, or suspect, that some might not do then make
> that knowledge explicit (at least by not listing all similar
> packages). All the packages providing *tags are probably
> pretty equivalent, but yacc, byacc, bison etc. have differences
> that mean that some gr
If you know, or suspect, that some might not do then make
that knowledge explicit (at least by not listing all similar
packages). All the packages providing *tags are probably
pretty equivalent, but yacc, byacc, bison etc. have differences
that mean that some grammars are not acceptable to all of t
On Fri, Nov 12, 1999 at 08:13:54PM +, David Coe wrote:
> Yacc and ctags are provided by many different packages, and managed
> by update-alternatives, but there is no virtual package corresponding
> to either of them.
...
> What should I do? Thanks.
Contact the maintainers of such packages a
iirc this exact situation was discussed rather recently with
some other package, and the result was that there is one /main
source archive. The division to '/us' and /non-us is not
important, especially now when apt can hide it from the user.
This would imply one source in /non-us and two binaries
If this has already been discussed, please just point me to it; I must
have missed it...
Yacc and ctags are provided by many different packages, and managed
by update-alternatives, but there is no virtual package corresponding
to either of them.
I suspect there are other similar situations.
I do
>
> Or can I upload everything to non-us and produce two binary
> packages (one for regular main and the other for non-us/main)?
> I have the feeling this is not allowed because it makes the
> source hard to find. Right?
>
I would believe you are right. Two source archives it is )-:
The latest upstream version of powstatd comes in two favours,
regular and one that use 128-bit TEA encryption for communication
between master and slave.
Currently, the upstream author is producing two source archives
(but we are discussing this). The only difference is that one
doesn't include
On Thu, Nov 11, 1999 at 07:57:41PM +0100, Miquel van Smoorenburg wrote:
> According to [EMAIL PROTECTED]:
> > The original bug report says:
> > Since `dhcpcd' is executed at startup
> > (in /etc/init.d/dhcpcd or /etc/init.d/networking) before
> > /etc/init.d/bootmisc.sh, these files are remov
8 matches
Mail list logo
