Hi!

Azt sajnos nem tudom, hogy a swarettel vagy slapt-gettel mi a helyzet – nem ismerem ezek mûködését. De az így telepített progi biztosan bekerül a ‘pkg adatbázisba’ (/var/log/packages), mivel a checkinstall script elõször csomagot készít a lefordított progiból (makepak scripttel), majd telepíti azt (installpkg scripttel).

swarettel ill. slapt-gettel kapcsolatban szerintem csak az a kérdés, hogy hol vannak nyilvántartva az adott csomag függõségei. Ha vmi netes adatbázisban, akkor semmi gond (ugyanúgy fog viselkedni, mint bármelyik másik csomi). Ha a csomagban valahol, akkor passz…

nekem fenn van a 9.1 ebbõl hogyan tudok Current-et csinálni neten keesztül?

Bakker ezt találtam…
http://gnome-pkgtool.sourceforge.net/

Hi!

Paca, nem semmi progikat találsz te mostanában. 🙂
Nem tudod, a fenti kettõbõl van ami a a függõségeket is figyelné, olyan swaret szerûen?

Megnéztem ennek a gnome-pkgtools nevü proginak configure –help kimenetét és ez van benne:

configure’ configures this package to adapt to many kinds of systems.

Usage: ./configure [OPTION]… [VAR=VALUE]…

To assign environment variables (e.g., CC, CFLAGS…), specify them as
VAR=VALUE.  See below for descriptions of some of the useful variables.

Defaults for the options are specified in brackets.

Configuration:
  -h, –help              display this help and exit
      –help=short        display options specific to this package
      –help=recursive    display the short help of all the included packages
  -V, –version          display version information and exit
  -q, –quiet, –silent  do not print `checking…’ messages
      –cache-file=FILE  cache test results in FILE [disabled]
  -C, –config-cache      alias for `–cache-file=config.cache’
  -n, –no-create        do not create output files
      –srcdir=DIR        find the sources in DIR [configure dir or `..’]

Installation directories:
  –prefix=PREFIX        install architecture-independent files in PREFIX
                          [/usr/local]
  –exec-prefix=EPREFIX  install architecture-dependent files in EPREFIX
                          [PREFIX]

By default, `make install’ will install all the files in
`/usr/local/bin’, `/usr/local/lib’ etc.  You can specify
an installation prefix other than `/usr/local’ using `–prefix’,
for instance `–prefix=$HOME’.

For better control, use the options below.

Fine tuning of the installation directories:
  –bindir=DIR          user executables [EPREFIX/bin]
  –sbindir=DIR          system admin executables [EPREFIX/sbin]
  –libexecdir=DIR      program executables [EPREFIX/libexec]
  –datadir=DIR          read-only architecture-independent data [PREFIX/share]
  –sysconfdir=DIR      read-only single-machine data [PREFIX/etc]
  –sharedstatedir=DIR  modifiable architecture-independent data [PREFIX/com]
  –localstatedir=DIR    modifiable single-machine data [PREFIX/var]
  –libdir=DIR          object code libraries [EPREFIX/lib]
  –includedir=DIR      C header files [PREFIX/include]
  –oldincludedir=DIR    C header files for non-gcc [/usr/include]
  –infodir=DIR          info documentation [PREFIX/info]
  –mandir=DIR          man documentation [PREFIX/man]

Program names:
  –program-prefix=PREFIX            prepend PREFIX to installed program names
  –program-suffix=SUFFIX            append SUFFIX to installed program names
  –program-transform-name=PROGRAM  run sed PROGRAM on installed program names

System types:
  –build=BUILD    configure for building on BUILD [guessed]
  –host=HOST      cross-compile to build programs to run on HOST [BUILD]

Optional Features:
  –disable-FEATURE      do not include FEATURE (same as –enable-FEATURE=no)
  –enable-FEATURE[=ARG]  include FEATURE [ARG=yes]
  –disable-dependency-tracking Speeds up one-time builds
  –enable-dependency-tracking  Do not reject slow dependency extractors
  –enable-shared[=PKGS]
                          build shared libraries [default=yes]
  –enable-static[=PKGS]
                          build static libraries [default=yes]
  –enable-fast-install[=PKGS]
                          optimize for fast installation [default=yes]
  –disable-libtool-lock  avoid locking (might break parallel builds)
  –disable-nls          do not use Native Language Support
  –disable-rpath        do not hardcode runtime library paths

Optional Packages:
  –with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]
  –without-PACKAGE      do not use PACKAGE (same as –with-PACKAGE=no)
  –with-gnu-ld          assume the C compiler uses GNU ld [default=no]
  –with-pic              try to use only PIC/non-PIC objects [default=use
                          both]
  –with-tags[=TAGS]
                          include additional configurations [automatic]
  –with-gnu-ld          assume the C compiler uses GNU ld default=no
  –with-libiconv-prefix[=DIR]  search for libiconv in DIR/include and DIR/lib
  –without-libiconv-prefix    don’t search for libiconv in includedir and libdir
  –with-included-gettext use the GNU gettext library included here
  –with-libintl-prefix[=DIR]  search for libintl in DIR/include and DIR/lib
  –without-libintl-prefix    don’t search for libintl in includedir and libdir

Some influential environment variables:
  CC          C compiler command
  CFLAGS      C compiler flags
  LDFLAGS    linker flags, e.g. -L if you have libraries in a
              nonstandard directory
  CPPFLAGS    C/C++ preprocessor flags, e.g. -I if you have
              headers in a nonstandard directory
  CPP        C preprocessor
  CXX        C++ compiler command
  CXXFLAGS    C++ compiler flags
  CXXCPP      C++ preprocessor
  F77        Fortran 77 compiler command
  FFLAGS      Fortran 77 compiler flags

Use these variables to override the choices made by `configure’ or to help
it to find libraries and programs with nonstandard names/locations.

Csemegézzzzz… 😀 😀 😀 😀

Végülis ez a gnome-pkgtool annyit csinál, hogy a fordítás végén a checkinstall progit hívja meg