public inbox for gentoo-osx@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grobian <grobian@gentoo.org>
To: gentoo-osx@lists.gentoo.org
Subject: Re: [gentoo-osx] The road ahead?
Date: Tue, 01 Nov 2005 18:26:35 +0100	[thread overview]
Message-ID: <4367A54B.1010606@gentoo.org> (raw)
In-Reply-To: <57628.84.179.212.58.1130864248.squirrel@mail.sz-online.de>

dirk.schoenberger@sz-online.de wrote:
> Sorry, but this attitude firmly belong into the "a GUI is just a frontend
> to the CLI" camp, where I don't really subscribe too. A CLI has its place,
> but a GUI does so, too, and both are not dependent upon.
> KDE / GNOME .desktop entries doesn't really compare to Apple's app
> folders, because .desktop entries are really just start scripts. An app
> folder contains starting scripts and the related resources / libraries in
> an all in one package. The idea is that you can copy an app folder around
> in your local file system or to another file system (thing .dmg here),
> while the application still remains runnable. So you have to include any
> library, beside the Apple provided ones.

I see your point, but I think it's a bit unrelated to Gentoo.  It might 
however be easier to accomplish with Gentoo because it compiles from 
sources and has more control on how a package is built.  Ideally one 
could do "ebuild myapp-1.0.ebuild osxapp" or something, just like 
"ebuild myapp-1.0.ebuild rpm" is there.  (Or was envisioned.)

>>> 1) packages which integrate nicely into the system (no dependencies, or
>>> dependencies which are properly provided by MacOS)
>> No collisions and no dependencies?  No reason to wait for gentoo-osx then.
> 
> No complicated dependencies. So this is the easiest part, where I still
> like to have Gentoo's safety net which keeps knowledge about what files
> belong to which package. This allows for clean uninstall, at least what
> concerns removing files. I am not quite sure about Fink style install and
> uninstall scripts.

Uninstalling fink is "rm -R /sw", uninstalling a separate package... 
well, must be possible, though I cannot remember having it done myself.

>>> 2) packages which clash with MacOS provided packages, things like python
>>> or automake spring to mind
>> And bash, ls, grep, emacs, vi, vim, gcc, perl, python, tcl/tk, apache,
>> etc. etc. etc.
> 
> python and automake are the cases which really annoy me, but naturally you
> are correct about the other packages, too. If possible I would like to use
> an Apple provided gcc, so this package is disputable.

Yes, me too, and especially the Apple linker! (ld)  But maybe Kito knows 
whether this linker can also be installed if the source is available.


-- 
Fabian Groffen
Gentoo for Mac OS X Project -- Interim Lead
-- 
gentoo-osx@gentoo.org mailing list



  reply	other threads:[~2005-11-01 17:27 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 22:17 [gentoo-osx] The road ahead? dirk.schoenberger
2005-10-31 23:12 ` Kito
2005-10-31 23:49   ` dirk.schoenberger
2005-11-01  7:33     ` Grobian
2005-11-01 16:07 ` Nathan
2005-11-01 16:28   ` Kito
2005-11-01 16:55     ` Nathan
2005-11-01 17:17     ` Grobian
2005-11-01 18:09       ` Nathan
2005-11-01 19:03         ` m h
2005-11-01 19:13           ` Grobian
2005-11-01 19:32             ` m h
2005-11-01 19:36               ` Grobian
2005-11-01 19:45                 ` m h
2005-11-01 19:14           ` Nathan
2005-11-01 16:57   ` dirk.schoenberger
2005-11-01 17:26     ` Grobian [this message]
2005-11-01 18:08     ` Nathan
  -- strict thread matches above, loose matches on Subject: below --
2005-11-01 19:35 dirk.schoenberger
2005-10-30 10:49 Grobian
2005-10-30 17:15 ` Stroller
2005-10-31  5:25 ` Lina Pezzella
2005-10-31 18:58   ` Grobian
2005-10-31 18:52 ` Kito
2005-10-31 19:34   ` Grobian
2005-10-31 21:42     ` Kito
2005-10-31 22:20       ` Grobian
2005-11-01 22:45     ` Lina Pezzella
2005-11-02  0:06       ` Kito
2005-11-02  7:29         ` Grobian
2005-11-01  0:16   ` m h
2005-11-01  0:32     ` Brian Harring
2005-11-01  0:59       ` Kito
2005-11-01 19:16         ` m h
2005-11-01 20:10           ` Kito
2005-11-01 20:16             ` Nathan
2005-11-01 20:21               ` Grobian
2005-11-01 20:37                 ` Kito
2005-11-01 20:45                   ` Grobian
2005-11-01 20:58                     ` Kito
2005-11-01 21:05                       ` Grobian
2005-11-01 22:01             ` m h
2005-11-01 22:55               ` Kito
2005-11-04 17:50                 ` m h
2005-11-08  1:48                   ` m h
2005-11-08 16:53                     ` Grobian
2005-11-08 17:09                       ` Kito
2005-11-08 21:10                         ` m h
2005-12-05  5:19                           ` m h
2005-12-05 17:20                             ` Kito
2005-11-02  2:33             ` Brian Harring
2005-11-02  3:00               ` Kito
2005-11-02  4:12                 ` Brian Harring
2005-11-02  4:16               ` Nathan
2005-11-02  5:52                 ` Brian Harring
2005-11-01  1:20       ` m h
2005-11-01  1:57         ` Brian Harring
2005-11-01  0:51     ` Kito

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=4367A54B.1010606@gentoo.org \
    --to=grobian@gentoo.org \
    --cc=gentoo-osx@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox