> Alexander Skwar:
> No, what I was thinking of, was it would be nice to be able to install a
> file in %{_mandir}, and that %{_mandir} would be expanded when the file is
> installed. Currently %{_mandir} may expand to /usr/man or /usr/share/man,
> depending on the distribution and version/relea
On Tue, Aug 08, 2000 at 05:14:45PM +0200, clemensF wrote:
> what do you mean by an install time macro? rpm's, but also tgz and the
> debian packager specify postinstall-scripts. you want propably a com-
> bination of this and automake?
No, what I was thinking of, was it would be nice to be able
> Alexander Skwar:
> > locations? For example, SuSE puts binaries for X in /usr/bin/X11. RPMs I've used
>to
> > upgrade apps keep putting X binaries in /usr/bin. (Is that the Red Hat standard?)
>
> And that's why an install time macro would be so handy. If this would be
> used, it wouldn't s
Am Mon, 07 Aug 2000 schrieben Sie:
> On Mon, Aug 07, 2000 at 11:48:20AM +0100, Alan Buxey <[EMAIL PROTECTED]> wrote:
> > 'specialised' and 'conventions' spell proprietary in my book.
> > whats wrong with the 'open' RPM standard embraced by the tools already on
> > most Linux, Solaris, Un8X system
On Mon, Aug 07, 2000 at 10:44:21AM -0400, Robb Kidd wrote:
> Isn't this mostly differences in a given distribution's choices about file
> locations? For example, SuSE puts binaries for X in /usr/bin/X11. RPMs I've used to
> upgrade apps keep putting X binaries in /usr/bin. (Is that the Red H
Marc Lehmann wrote:
> On Mon, Aug 07, 2000 at 11:48:20AM +0100, Alan Buxey <[EMAIL PROTECTED]> wrote:
> > 'specialised' and 'conventions' spell proprietary in my book.
> > whats wrong with the 'open' RPM standard embraced by the tools already on
> > most Linux, Solaris, Un8X systems?
>
> At least
Unsubscribe me please ... I'm getting bored of low-level mails,thanks.
On Mon, Aug 07, 2000 at 11:48:20AM +0100, Alan Buxey <[EMAIL PROTECTED]> wrote:
> 'specialised' and 'conventions' spell proprietary in my book.
>
> whats wrong with the 'open' RPM standard embraced by the tools already on
> most Linux, Solaris, Un8X systems?
At least according to daniel egger,
hi,
> No, that was not what I meant. Mandrake RPMs are about all compiled with the
> same settings, use a standard way to update menus for GNOME or KDE and store
> files like manpages in the same location (/usr/share/man/*). So, if you're
> using a Mandrake distribution, it is best to stay with
TED]
Thema: Re: Antwort: Re: GIMP v1.1.24 RPM Take 2
hi,
> mdk rpms are specialized RPMs that conform to the Mandrake RPM conventions.
'specialised' and 'conventions' spell proprietary in my book.
whats wrong with the 'open' RPM standard embraced by the tools a
hi,
> mdk rpms are specialized RPMs that conform to the Mandrake RPM conventions.
'specialised' and 'conventions' spell proprietary in my book.
whats wrong with the 'open' RPM standard embraced by the tools already on
most Linux, Solaris, Un8X systems?
best avoid those 'special blands' and ke
mdk rpms are specialized RPMs that conform to the Mandrake RPM conventions.
12 matches
Mail list logo
