" a task at present. You can remove
its task package... or you could hunt down all the task package's
dependencies and remove them. Under the proposed setup, tasksel could
mark all the packages making up the task for removal.
--
Charles Briscoe-Smith Hacking Free Soft
finger: /dev//merry.bs.lan:0: No such file or directory
LoginName Tty Idle Login Time Office Office Phone
cpb4 Charles Briscoe-Smith *:0Jul 7 02:20 (console)
cpb4 Charles Briscoe-Smith pt Jul 10 14:17 (merry.bs.lan:0.0)
cpb4 Ch
tice what you did, and switch that alteratives group to "manual mode",
so your changes are not lost.
HTH,
--
Charles Briscoe-Smith
My web page: http://www.debian.org/%7Ecpbs/>
PGP public keyprint: 74 68 AB 2E 1C 60 22 94 B8 21 2D 01 DE 66 13 E2
u suggest),
THEN they should be accompainied by mod times, sizes, ownerships,
modes and symlink destinations. Basically, everything that can
be stored in a tar file, except the actual file contents, which is
checksummed instead.
That probably wasn't worth the time I'v
d assume to be a good place to check, seems to be
down. Hmm...
--
Charles Briscoe-Smith
White pages entry, with PGP key: http://alethea.ukc.ac.uk/wp?95cpb4>
PGP public keyprint: 74 68 AB 2E 1C 60 22 94 B8 21 2D 01 DE 66 13 E2
grade, because the
diversion is already installed. It doesn't need to be called on purge,
because the package can only be purged after it has been removed; the
diversion will already have been removed.
--
Charles Briscoe-Smith
White pages entry, with PGP key: http://alethea.ukc.ac.uk/wp?95cpb4
(or don't want) a local flag-day.)
- - -
I know I'm producing a -lot- of hot air here, and no code. I don't know
dpkg's internals at the moment, but I'm willing to try learning it and
help implement this thing if anyone thinks it's a good idea.
Finally, Ian, wo
ager that it should not be.
My guess is that whoever wrote that README was thinking the same way.
--
Charles Briscoe-Smith
White pages entry, with PGP key: http://alethea.ukc.ac.uk/wp?95cpb4>
PGP public keyprint: 74 68 AB 2E 1C 60 22 94 B8 21 2D 01 DE 66 13 E2
ur `fhs-transition' script, and decide to invoke it. Some version
of our distribution might be FHS compliant, but upgrading a system to
that version wouldn't make the system FHS compliant. The benefits of
/usr/share are not realised until the sysadmin takes the time to make
it so.
With the scheme I outlined above, the system is FHS compliant as soon
as all of its packages are FHS compliant. The sysadmin never has to sit
down and work on his system to make it compliant and reap the benefits.
Surely this is the purpose of using a distribution?
--
Charles Briscoe-Smith
White pages entry, with PGP key: http://alethea.ukc.ac.uk/wp?95cpb4>
PGP public keyprint: 74 68 AB 2E 1C 60 22 94 B8 21 2D 01 DE 66 13 E2
PS: Apologies for subjecting you all to such a long rant...
Adam P. Harris writes:
>[BTW, should I CC both the BTS *and* debian-policy?]
I believe the BTS forwards anything it receives to the package's
maintainer, debian-policy. I only got one copy from the list, though,
so I suspect the list server suppresses duplicates.
>Charles Briscoe-Sm
ackages to scroll away, so that I don't
get a chance to read it. But that has nothing to do with the ldconfig
proposal...]
[1] The output from wdiff, as distinct from "normal" patch output from
diff. For those unfamiliar with wdiff, {+ ... +} indicates additions,
[- .
al are kept outside of the
/usr partition. The symlinks in /usr-overflow are simply the ones I
happened to find where needed; it probably be simpler just to symlink
everything from /usr into /usr-overflow, then delete the ones to be moved.
Symlinks to top-level direcrories work with no other changes, of
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
>Hi,
Hello.
>>>"Charles" == Charles Briscoe-Smith <[EMAIL PROTECTED]> writes:
> Charles> "Non-software"? Data is software, isn't it?
>
> Not as the term is commonly used.
Granted; b
uld be treated just like
works of static fiction.
Hmm. How do we distinguish between program and data? Perhaps we use the
definition that, IIRC, some judge used (according to slashdot); that of
whether it is a 'functional device'. If the software can (instruct a
computer to) perform a real-wo
hack sometime
(possibly a long time) after the next stable release. I'd say you should
probably keep upgradability from all versions of your package which have
been part of a 'stable' release, though.
--
Charles Briscoe-Smith
White pages entry, with PGP key: http://alethea.uk
erly
configurable. I'll try to do this sometime, but it may not be soon,
because I'm busy with my PhD just now (process algebras and behavioural
subtyping, in case anyone's interested in knowing that...) If anyone else
would like to work up something practical based on this idea, please do.
meta-meta-meta-policy you just stated, "No, there won't be a
meta-meta-policy"? Doesn't your next sentence point to a need for an
exception to this meta-meta-meta-policy? What we -really- need is a
meta-meta-meta-meta-policy to clear up this frightfully unclear situation
once a
e, but if you
can still `patch' it easily, it's okay, right?
--
Charles Briscoe-Smith
White pages entry, with PGP key: http://alethea.ukc.ac.uk/wp?95cpb4>
PGP public keyprint: 74 68 AB 2E 1C 60 22 94 B8 21 2D 01 DE 66 13 E2
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
o non-free/intepreters or leave it as-is?
I'd appreciate your opinions.
--
Charles Briscoe-Smith
White pages entry, with PGP key: http://alethea.ukc.ac.uk/wp?95cpb4>
PGP public keyprint: 74 68 AB 2E 1C 60 22 94 B8 21 2D 01 DE 66 13 E2
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
ld be similar to hosts.{allow,deny}: run-parts would, for
each script, run it if its name is in run.allow, otherwise not run it if
its name is in run.deny, otherwise run it anyway. base-files or similar
can provide conffiles /etc/ppp/ip-{up,down}/run.deny containing a "*"
to make the defa
no harm.
True, they aren't standard or mandated by policy, but neither are
md5sums files. For now, these are both experimental and optional.
People, please don't forbid `du' control files unless you also forbid
`md5sums'.
Thanks,
--
Charles Briscoe-Smith
White pages entry,
-> /home/overflow/usr/doc
A front-end can easily cope with this. For the strn example, it means
that 115 blocks goes on /dev/hda6 (/home), and 508-115=393 blocks goes
on /dev/hda7 (/usr). See how easy it is to work all this out?
The tools to exploit this information aren't here yet, bu
sing these YET. If we decide to keep
them, though, they will be useful for a FUTURE package manager.
>If there is no good reason for these files, should we consider this a bug?
>(IMO, yes.)
They are an experimental feature, like the md5sums files. We have no
policy against md5sums files, do
s always a /bin/sh installed,
even when bash isn't essential, would be to have all the editors "Provide:
posix-sh" and have another essential package depend on posix-sh.
Preferably the chosen package would be one that actually uses sh...
sysvinit for example. A lot of base packages
nual/ch-sourcepkg.html#s-dpkgchangelog
Closes would be a keyword, like urgency, and can be handled by the current
keyword=value system, just like urgency. It should be something like
foo (1.0-2) unstable; urgency=low, closes=10002 11930 10109
--Charles Briscoe-Smith
White pages entry, with PGP k
25 matches
Mail list logo
