Josip Rodin [EMAIL PROTECTED] writes:
Right, but what I'm asking is how to include a handful of
plaintext files with filesystem locations in an otherwise
empty task-* package. Should I make a custom Makefile or
have I missed a useful dpkg tool to help with this?
Just use install -m
Are you planning to set up an autobuilder for s390?
Yes, I am currently working on it.
--
Gerhard
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hello,
I'm about to upload replicator (replicator.sourceforge.net at present)
on master but I have some questions:
- there's no postrm script yet althougth there's a real need for that.
Should I write it before uploading?
- I'd like to engage many discussion about replicator on debian
Putting -all- the plugins in one package would be nice but I don't know
how happy users will be if they are forced to download a truckload of
extra libs they may not want. I'll probably add a top level pseudo
package depending on all the other packages just for user convenience.
Perhaps
Suppose version 1 of the package had a file named /foo/A,
and version 2 had changed the location to be /bar/A.
Without doing anything special on the part of the developer, is it
always true that upgrading the package version 1-2 will remove /foo/A
before installing /bar/A?
If so, has there ever
Hello,
thanks for this short/efficient anwser.
[EMAIL PROTECTED] wrote:
this
may change in the future if my proposition to debian policy are
accepted. Do you think this is possible?
What proposition?
To replicate a Debian system we need to know which configuration files
are
On Thu, May 17, 2001 at 11:38:06AM -0400, Steve M. Robbins wrote:
Suppose version 1 of the package had a file named /foo/A,
and version 2 had changed the location to be /bar/A.
Without doing anything special on the part of the developer, is it
always true that upgrading the package version
On Thu, May 17, 2001 at 10:12:29AM +0200, Robert Bihlmeyer wrote:
Right, but what I'm asking is how to include a handful of
plaintext files with filesystem locations in an otherwise
empty task-* package. Should I make a custom Makefile or
have I missed a useful dpkg tool to help with
To replicate a Debian system we need to know which configuration files
are replicable and which ones are not.
What would you consider to be non-replicable?
I would imagine that there would be few enough of such files that you could
keep track of them internally to your package.
The word
On Thu, May 17, 2001 at 07:36:34PM +0200, Josip Rodin wrote:
On Thu, May 17, 2001 at 11:38:06AM -0400, Steve M. Robbins wrote:
Suppose version 1 of the package had a file named /foo/A,
and version 2 had changed the location to be /bar/A.
Without doing anything special on the part of the
On 15 May 2001 09:16:10 +0200, Jens Schmalzing
[EMAIL PROTECTED] wrote:
Marc Haber writes:
All three of these packages are quite large packages with a lot of
framework. Actually, I was hoping that there is a package that
simpily includes a kernel module, for example a network driver, that
I
On Mon, May 14, 2001 at 10:32:07AM +0200, Robert Bihlmeyer wrote:
Jimmy Kaplowitz [EMAIL PROTECTED] writes:
Choice 3: Just change the main althea package to include ssl
support, and add to the package description and README.Debian
notification to that effect, with instructions on how to
On Thu, May 17, 2001 at 12:48:14PM +0200, [EMAIL PROTECTED] wrote:
Are you planning to set up an autobuilder for s390?
Yes, I am currently working on it.
Would you be willing to grant developer accounts on such a system? I am very
interested in working on the s390 port, but I don't have
* Matt Zimmerman [EMAIL PROTECTED] [20010517 18:31]:
Are you planning to set up an autobuilder for s390?
Yes, I am currently working on it.
Would you be willing to grant developer accounts on such a system? I am very
interested in working on the s390 port, but I don't have any hardware
I just adopted xabacus.
It conflicts with xmabacus because both try to install
the same config file /etc/X11/app-defaults/Abacus.
Policy is really strict about this :
11.7.4 Sharing configuration files
Packages which specify the same file as `conffile' must be tagged as
conflicting
Josip Rodin [EMAIL PROTECTED] writes:
Right, but what I'm asking is how to include a handful of
plaintext files with filesystem locations in an otherwise
empty task-* package. Should I make a custom Makefile or
have I missed a useful dpkg tool to help with this?
Just use install -m
subscribe
Are you planning to set up an autobuilder for s390?
Yes, I am currently working on it.
--
Gerhard
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net
Hello,
I'm about to upload replicator (replicator.sourceforge.net at present)
on master but I have some questions:
- there's no postrm script yet althougth there's a real need for that.
Should I write it before uploading?
- I'd like to engage many discussion about replicator on debian
- there's no postrm script yet althougth there's a real need for that.
Should I write it before uploading?
Yes, of course. All packages should install and uninstall cleanly before
being uploaded.
- I'd like to engage many discussion about replicator on debian lists.
Should I wait for the
Putting -all- the plugins in one package would be nice but I don't know
how happy users will be if they are forced to download a truckload of
extra libs they may not want. I'll probably add a top level pseudo
package depending on all the other packages just for user convenience.
Perhaps
Suppose version 1 of the package had a file named /foo/A,
and version 2 had changed the location to be /bar/A.
Without doing anything special on the part of the developer, is it
always true that upgrading the package version 1-2 will remove /foo/A
before installing /bar/A?
If so, has there ever
Hello,
thanks for this short/efficient anwser.
[EMAIL PROTECTED] wrote:
this
may change in the future if my proposition to debian policy are
accepted. Do you think this is possible?
What proposition?
To replicate a Debian system we need to know which configuration files
are
Dave Baker [EMAIL PROTECTED] writes:
My opinion only - 30 and growing is too large. Group the plugins by type
if possible.
That's preferrable. What does your list of packages currently look
like?
I might prefer to download a little more if I use it than
have everyone else suffer through
On Thu, May 17, 2001 at 11:38:06AM -0400, Steve M. Robbins wrote:
Suppose version 1 of the package had a file named /foo/A,
and version 2 had changed the location to be /bar/A.
Without doing anything special on the part of the developer, is it
always true that upgrading the package version
On Thu, May 17, 2001 at 10:12:29AM +0200, Robert Bihlmeyer wrote:
Right, but what I'm asking is how to include a handful of
plaintext files with filesystem locations in an otherwise
empty task-* package. Should I make a custom Makefile or
have I missed a useful dpkg tool to help with
To replicate a Debian system we need to know which configuration files
are replicable and which ones are not.
What would you consider to be non-replicable?
I would imagine that there would be few enough of such files that you could
keep track of them internally to your package.
The word
On Thu, May 17, 2001 at 07:36:34PM +0200, Josip Rodin wrote:
On Thu, May 17, 2001 at 11:38:06AM -0400, Steve M. Robbins wrote:
Suppose version 1 of the package had a file named /foo/A,
and version 2 had changed the location to be /bar/A.
Without doing anything special on the part of the
On 15 May 2001 09:16:10 +0200, Jens Schmalzing
[EMAIL PROTECTED] wrote:
Marc Haber writes:
All three of these packages are quite large packages with a lot of
framework. Actually, I was hoping that there is a package that
simpily includes a kernel module, for example a network driver, that
I
On Mon, May 14, 2001 at 10:32:07AM +0200, Robert Bihlmeyer wrote:
Jimmy Kaplowitz [EMAIL PROTECTED] writes:
Choice 3: Just change the main althea package to include ssl
support, and add to the package description and README.Debian
notification to that effect, with instructions on how to
On Thu, May 17, 2001 at 12:48:14PM +0200, [EMAIL PROTECTED] wrote:
Are you planning to set up an autobuilder for s390?
Yes, I am currently working on it.
Would you be willing to grant developer accounts on such a system? I am very
interested in working on the s390 port, but I don't have
* Matt Zimmerman [EMAIL PROTECTED] [20010517 18:31]:
Are you planning to set up an autobuilder for s390?
Yes, I am currently working on it.
Would you be willing to grant developer accounts on such a system? I am very
interested in working on the s390 port, but I don't have any hardware
I just adopted xabacus.
It conflicts with xmabacus because both try to install
the same config file /etc/X11/app-defaults/Abacus.
Policy is really strict about this :
11.7.4 Sharing configuration files
Packages which specify the same file as `conffile' must be tagged as
conflicting
33 matches
Mail list logo
