I wrote:
> you like, checksums) of files more easily. If there were a standard
> file registration scheme for files which were in the .deb's filesystem
> archive, [...]
I meant "weren't"
Ian.
--
To UNSUBSCRIBE, email to debian-devel-requ...@list
sean finney writes ("Re: Atlas proposal [and 1 more messages]"):
> as an admin i'd be very annoyed by that behavior, because there's no way
> for me to know what package the file came from then, or whether it was my
> own accidental actions that led to it (i
On Wed, Aug 25, 2010 at 06:46:18PM +0100, Ian Jackson wrote:
> Goswin von Brederlow writes ("Re: Atlas proposal [and 1 more messages]"):
> > Just dumping the compiled files into /usr/lib/ I find quite unacceptable
> > too.
>
> No, it is absolutely fine and it is wh
Goswin von Brederlow writes ("Re: Atlas proposal [and 1 more messages]"):
> Just dumping the compiled files into /usr/lib/ I find quite unacceptable
> too.
No, it is absolutely fine and it is what atlas-auto should do. It is
a simple matter for its postinst and postrm to deal
Ian Jackson writes:
> Goswin von Brederlow writes ("Re: Atlas proposal"):
>> I also have a package "local-archive" that depends on reprepro,
>> generates a local signing key on first install, adds that to the apt-get
>> keyring and adds a file:/// url in /etc/apt/sources.list.d/.
>
> I think this
Goswin von Brederlow writes ("Re: Atlas proposal"):
> I also have a package "local-archive" that depends on reprepro,
> generates a local signing key on first install, adds that to the apt-get
> keyring and adds a file:/// url in /etc/apt/sources.list.d/.
I think this scheme is a very bad idea. I
6 matches
Mail list logo
