On Wed, Aug 18, 1999 at 11:55:35AM -0700, Joey Hess wrote:
> > But in this case, wouldn't it be more useful to have them all available
> > everywhere, so that when you're making use of the examples you can get at
> > all the data formats at once, without having to have a machine running
> > each di
Anthony Towns wrote:
> Why would we have architecture specific examples? The only reason I can
> think of is to help specify a data format that differs across platforms
> (example programs should be given in source).
Think about things like example data files with endian issues.
> But in this cas
On Tue, Aug 17, 1999 at 12:53:34PM -0700, Joey Hess wrote:
> How about this:
> Any examples (configurations, source files, whatever), should be
> installed in a directory /usr/share/doc//examples'. These
> files should not be referenced by any program--they're there
> for the benefi
-BEGIN PGP SIGNED MESSAGE-
Joey Hess <[EMAIL PROTECTED]> writes:
> + only. Architecture-specific example files should be installed in a directory
> + /usr/lib//examples, and files in
> + /usr/share/doc//examples symlink to files in it. Or the latter
> directory may be a symlink to the f
Chris Waters wrote:
> > + only. Architecture-specific example files should be installed in a
> > directory
> > + /usr/lib//examples, and files in
> > + /usr/share/doc//examples symlink to files in it. Or the latter
> > directory may be a symlink to the former.
>
> Yes, that will definitely do.
-BEGIN PGP SIGNED MESSAGE-
Joey Hess <[EMAIL PROTECTED]> writes:
> + only. Architecture-specific example files should be installed in a directory
> + /usr/lib//examples, and files in
> + /usr/share/doc//examples symlink to files in it. Or the latter
> directory may be a symlink to the f
Chris Waters wrote:
> > I presume (as I mentioned in my seconding of the proposal) that Joey
> > means a symlink such as
>
> > /usr/share/doc//examples/bin -> /usr/lib//examples
>
> Yes, but it needs to *say* that. Let's get the corrections in first,
> *then* start the seconding process! :-)
>
Jim Lynch wrote:
> >From the description "arch dep goes in /usr/lib//examples
> with symlink to /usr/doc//examples ",
> I cannot visualize the tree. For one, how would one distinguish
> arch-indep stuff from the arch-specific?
Whatever works. I made that posposfully vaguse so people can do anythi
Julian Gilbey <[EMAIL PROTECTED]> writes:
> I presume (as I mentioned in my seconding of the proposal) that Joey
> means a symlink such as
> /usr/share/doc//examples/bin -> /usr/lib//examples
Yes, but it needs to *say* that. Let's get the corrections in first,
*then* start the seconding process
Processing commands for [EMAIL PROTECTED]:
> retitle 42849 [PROPOSED] FHS-compliant location of compiled examples
Bug#42849: er
Changed bug title.
> severity 42849 wishlist
Bug#42849: [PROPOSED] FHS-compliant location of compiled examples
Severity set to `wishlist'.
> close 42857
retitle 42849 [PROPOSED] FHS-compliant location of compiled examples
severity 42849 wishlist
close 42857
thanks
My bug report #42857 was actually intended to be a second to Joey's
proposal -- it may have got lost in the BTS (having been submitted
with subject "er"
> Hi,
>
> From the description "arch dep goes in /usr/lib//examples
> with symlink to /usr/doc//examples ",
> I cannot visualize the tree. For one, how would one distinguish
> arch-indep stuff from the arch-specific?
I presume (as I mentioned in my seconding of the proposal) that Joey
means a sy
> Any examples (configurations, source files, whatever), should be
> installed in a directory `/usr/share/doc//examples'. These
> files should not be referenced by any program--they're there
> for the benefit of the system administrator and users, as documentation
> - only.
> + only. Archit
Hi,
>From the description "arch dep goes in /usr/lib//examples
with symlink to /usr/doc//examples ",
I cannot visualize the tree. For one, how would one distinguish
arch-indep stuff from the arch-specific?
/
|
usr
|
Package: debian-policy
Chris Waters wrote:
> Joey Hess <[EMAIL PROTECTED]> writes:
>
> > I'd rather have /usr/lib/package/exmaples, with
> > /usr/share/doc/package/examples linking to it.
>
> Yes, that seems like the most appropriate way to deal with example
> binaries. Lets hope, though, that
Joey Hess <[EMAIL PROTECTED]> writes:
> I'd rather have /usr/lib/package/exmaples, with
> /usr/share/doc/package/examples linking to it.
Yes, that seems like the most appropriate way to deal with example
binaries. Lets hope, though, that example binaries is not something
that we have to deal wit
Manoj Srivastava wrote:
> Since they are jsut examples, I think they can be classified
> as akin to documentation, and still go in the usual place, namely,
> /usr/share/doc/package/*. There is no harm done, and no loss of
> functionality.
Well there's a small loss, should someone actual
Hi,
>>"Joey" == Joey Hess <[EMAIL PROTECTED]> writes:
Joey> I just realized something. With all this furur over /usr/share/doc,
Joey> we seem to have skipped right over the question of where do
arch-dependant
Joey> example files go. Where?
Since they are jsut examples, I think they ca
On Sun, Aug 08, 1999 at 10:11:56AM -0700, Joey Hess wrote:
> I just realized something. With all this furur over /usr/share/doc,
> we seem to have skipped right over the question of where do arch-dependant
> example files go. Where?
/usr/bin. =p
--
Joseph Carter <[EMAIL PROTECTED]>
I just realized something. With all this furur over /usr/share/doc,
we seem to have skipped right over the question of where do arch-dependant
example files go. Where?
--
see shy jo
20 matches
Mail list logo
