From: Till Kamppeter <till.kamppeter@gmail.com>
To: Robert Krawitz <rlk@alum.mit.edu>
Cc: printing-architecture@lists.freestandards.org,
printing-summit@lists.linux-foundation.org
Subject: Re: [Printing-summit] Re: [Printing-architecture] Posted OPS Summary from Montreal
Date: Thu, 18 Oct 2007 22:10:37 +0100 [thread overview]
Message-ID: <4717CBCD.7080302@gmail.com> (raw)
In-Reply-To: <200710161227.l9GCRgdF002017@dsl092-065-009.bos1.dsl.speakeasy.net>
Robert Krawitz wrote:
> Date: Tue, 16 Oct 2007 10:26:03 +0100
> From: Till Kamppeter <till.kamppeter@gmail.com>
>
> Robert Krawitz wrote:
> > Question:
> >
> > - Installing everything in /opt/<supplier>/ to avoid conflicts with
> > distribution
> >
> > What does this mean for Gutenprint or other similar packages?
> >
>
> This means that for distribution-independent LSB packages the
> "./configure; make; make install" sequence has to be called with
> different selections of installation directories and the
> post-install script of the package has to add directories to the
> $PATH and links to system locations.
>
> I didn't ask the right question: what is the value of <supplier>?
>
It is the name of the company for printer manufacturers and commercial
driver suppliers, the name of the project for free software projects. So
for you it is "gutenprint" (see my already existing packages).
Till
prev parent reply other threads:[~2007-10-18 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 18:42 [Printing-architecture] Posted OPS Summary from Montreal Ira McDonald
2007-10-15 19:57 ` Till Kamppeter
2007-10-15 20:15 ` Till Kamppeter
[not found] ` <200710152346.l9FNkVXZ018939@dsl092-065-009.bos1.dsl.speakeasy.net>
2007-10-16 9:26 ` [Printing-summit] " Till Kamppeter
[not found] ` <200710161227.l9GCRgdF002017@dsl092-065-009.bos1.dsl.speakeasy.net>
2007-10-18 21:10 ` Till Kamppeter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4717CBCD.7080302@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=printing-architecture@lists.freestandards.org \
--cc=printing-summit@lists.linux-foundation.org \
--cc=rlk@alum.mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.