The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

UPM: RPM and writing package with an editor

On Mon, 13 Jan 1997, Andreas Jellinghaus wrote:

aj >ok for me, but simple enough for everyone ? what about changing the
aj >format the way, it will invoka a shell, check for presence of upm, give
aj >a warning if it isn't installed and ask for creating a tar.gz or
aj >something like that ? 

The package manager has so many features not present on a bare system that
this is really not feasable. If someone wants to hack then let him hack
but not with an easy user interface.

aj >> debmake (and suidmanager) are in some respects trying to fix issues that
aj >> should properly be handled in the package managers. That is one of the
aj >> reasons for upm. debmake will certainly be developed alongside upm...
aj >
aj >i yust thought, if you have a package creator, to create also .rpm files
aj >wich must be easy to use and have advatages over current package
aj >creators - maybe also other programmer will use it. and that will help
aj >debian. 

Hmm. Perhaps someone could write a reverse converter UPM->RPM? It should
theoretically be easy since most of the concepts of rpm are included in
upm.

aj >> The ability to use an editor on the package file to fix small issues (like
aj >> a broken dependency, typo in installation scripts) is very important for
aj >> me. Also I would like to be able to review the installation scripts by
aj >> simply listing the package.
aj >
aj >using an editor to check a package and correct it  is a great thing, but
aj >using an editor to create a package will be no. one cause for such bugs.

Think about the following simple package:

#!/bin/upm
Package: myxgames
Flags: Meta
Depends: pacman, xpacman, xgal, xbill, xboing, fvwm95
%end

I have a number of machines to administer and having the ability to write
a short package like that would ease the job of making sure a certain
functionality exists on each of the systems.

Also the ability to write small packages with an editor can be used to
"package" up locally installed files.

Examples:

#!/bin/upm
Package: localprograms
Flags: Fake
%files
/usr/local/bin/l
/usr/local/bin/menu
/usr/local/bin/msac
/usr/local/bin/rmore
%end

Installing such a package would group the indicated files into a new
package localprograms (fake means dont install referenced files just
accept their presence on the system).

After the grouping of files in this manner I could simply transfer the
files to another host with

upm -b localprograms | rsh otherhost upm

--- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ ---
Please always CC me when replying to posts on mailing lists.


--
Please respect the confidentiality of material on the debian-private list.
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-private-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com