On Tue, Nov 25, 2003 at 08:40:43PM -0500, Igor Pechtchanski wrote:
BTW, another piece of non-setup information that might be useful is an up
for adoption (or orphaned) flag.
Why not make it a setup flag? Make a nasty little pop-up box pop up when you
install an orphaned package - something like
On Wed, 26 Nov 2003, Ronald Landheer-Cieslak wrote:
On Tue, Nov 25, 2003 at 08:40:43PM -0500, Igor Pechtchanski wrote:
BTW, another piece of non-setup information that might be useful is an up
for adoption (or orphaned) flag.
Why not make it a setup flag? Make a nasty little pop-up box pop
On Wed, Nov 26, 2003 at 10:19:12AM -0500, Igor Pechtchanski wrote:
On Wed, 26 Nov 2003, Ronald Landheer-Cieslak wrote:
On Tue, Nov 25, 2003 at 08:40:43PM -0500, Igor Pechtchanski wrote:
BTW, another piece of non-setup information that might be useful is an up
for adoption (or orphaned) flag.
On Wed, Nov 26, 2003 at 10:16:38AM -0500, Igor Pechtchanski wrote:
On Tue, 25 Nov 2003, Christopher Faylor wrote:
On Wed, Nov 26, 2003 at 03:10:51AM +, David F wrote:
) We could decide on a comment convention for setup.hint that could be
) used for some other tool to process:
)
)
It's a bit contrived, but...
A *bit* contrived?
Certainly not a byte contrived. A nybble contrived perhaps?
~$ ./setup.hint
bash: ./setup.hint: binary-only: bad interpreter: No such file or
directory
Perhaps the special comment should be something other than the shebang?
Just a thought.
I
On Tue, 25 Nov 2003, Daniel Reed wrote:
[snip]
The current attributes I use in apps.xml are:
binary-only (no lack-of-source checks)
ignore-before=X (ignore new versions less than or equal to X)
ignore-freshmeat (for Cygwin-specific packages)
maintainer (just the name)
) We could decide on a comment convention for setup.hint that could be
) used for some other tool to process:
)
) #!binary only
That works, or maybe even #!binary-only and either let multiple flags be on
one line or allow flags to have arguments.
It's a bit contrived, but...
~$ ./setup.hint
bash:
On 2003-11-24T11:01-0500, Christopher Faylor wrote:
) On Mon, Nov 24, 2003 at 10:55:40AM -0500, Daniel Reed wrote:
) For now it's just in my records. Even if it is made publicly tunable, I
) imagine it will be made outside of setup.hint (since that is for setup's
) benefit).
) We could decide on a
On Mon, Nov 24, 2003 at 11:17:51PM -0500, Daniel Reed wrote:
On 2003-11-24T11:01-0500, Christopher Faylor wrote:
) On Mon, Nov 24, 2003 at 10:55:40AM -0500, Daniel Reed wrote:
) For now it's just in my records. Even if it is made publicly tunable, I
) imagine it will be made outside of setup.hint
