[Fink-devel] Deprecating Postfix-release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey all, I want to make the postfix package track releases and deprecate postfix-release. There are a couple of problems with this, which I've already mailed the list about (Upgrading postfix): 1) postfix uses MMDD versioning schemes, but the upstream package is versioned M.m.b. Solution: continue using the MMDD scheme until someone implements epochs or whatever it is that would allow this to be fixed. 2) postfix-release needs to be deprecated. Solution 1: Simply stop updating it and add a note to the description that it is deprecated. Solution 2: Update it to an empty package the mails root about it being deprecated in PostInstScript. Solution 3: ??? Comments? I prefer the second solution for problem two, since it will result in more people upgrading right away. I want to deprecate postfix-release because I don't want to have to update postfix every time a new snapshot come out, and because it seems like overkill to have four plus postfix packages (there will be a -tls package). If I don't get any objections in the next few days, I'll go ahead. Thanks, Daniel - -- Moderation in all things, but most importantly, in moderation. My PGP public key: http://mwdesign.dyndns.org/~daniel/publickey.txt Don't use PGP? Check out http://www.pgpi.org/doc/whypgp/en/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (Darwin) iD8DBQE+E/MkxIklpV9nwSURAjvcAKDzFxDM9SoBolHgd4xYdDpsNAu0BQCgi6La FZdXZyjv/un9RKzFQcRINQg= =DUqW -END PGP SIGNATURE- --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Deprecating Postfix-release
Daniel Parks [EMAIL PROTECTED] wrote: Hey all, I want to make the postfix package track releases and deprecate postfix-release. There are a couple of problems with this, which I've already mailed the list about (Upgrading postfix): 1) postfix uses MMDD versioning schemes, but the upstream package is versioned M.m.b. Solution: continue using the MMDD scheme until someone implements epochs or whatever it is that would allow this to be fixed. 2) postfix-release needs to be deprecated. Solution 1: Simply stop updating it and add a note to the description that it is deprecated. Solution 2: Update it to an empty package the mails root about it being deprecated in PostInstScript. Solution 3: ??? Comments? I prefer the second solution for problem two, since it will result in more people upgrading right away. I want to deprecate postfix-release because I don't want to have to update postfix every time a new snapshot come out, and because it seems like overkill to have four plus postfix packages (there will be a -tls package). If I don't get any objections in the next few days, I'll go ahead. Hi Daniel. Why don't you just stick with the name postfix-release, and deprecate postfix? Here's a way it could be done: Replace postfix by an empty package which depends on postfix-release. You'll need to make a versioned dependency, to a new version of postfix-release which does *not* conflict with the new postfix (although it could still conflict with old versions of postfix). The way I would handle the deprecation would not be to send email to root, which might not be seen by a lot of Fink users, but instead to echo a message to the screen during post-install which says something like The postfix package is obsolete and can be removed; its functionality is now supplied by postfix-release. If, at some point in the future, we do get the epoch support, you could change the name to postfix at that time. Best, Dave --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Deprecating Postfix-release
[EMAIL PROTECTED] (Daniel Parks) wrote : Solution 2: Update it to an empty package the mails root about it being deprecated in PostInstScript. Solution 3: ??? Comments? I prefer the second solution for problem two, since it will result in more people upgrading right away. Don't forget that local mail is by default disabled in MacOSX, whith a .forward containing /dev/null in root homedir. Anyway, sendmail config is broken :-) -- Xavier http://www.freetibet.org http://www.tibet.fr/ --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Problems with net-snmp and netinet headers in 10.2.3
On Wednesday, Jan 1, 2003, at 20:08 US/Eastern, Jeremy Higgs wrote:
Hi everyone,
Justin Hallett alerted me to the fact that many of the headers (all?)
that were missing in 10.2 have been added to 10.2.3, so that the
jaguar-missing-headers package is no longer needed. I tried
recompiling net-snmp, one of the packages of mine that requires the
missing headers (but is not in unstable, as there were other missing
headers), and got this error:
Looks like one of the added headers is still dysfunctional. Grr... I
don't know personally which one this is, though...
mibII/tcp.c: In function `var_tcp':
mibII/tcp.c:287: storage size of `tcpstat' isn't known
mibII/tcp.c:287: storage size of `tcpstat' isn't known
Probably references like:
void foo(void) {
struct tcpstat *bar;
struct tcpstat quux;
}
but tcpstat are not defined when it should be, probably because of a
bad header.
mibII/tcp.c: At top level:
mibII/tcp.c:464: warning: `struct tcpstat' declared inside parameter
list
mibII/tcp.c:465: conflicting types for `read_tcp_stat'
mibII/tcp.c:278: previous declaration of `read_tcp_stat'
void foo(struct tcpstat *bar); -- tcpstat is still not defined
mibII/tcp.c: In function `read_tcp_stat':
mibII/tcp.c:586: dereferencing pointer to incomplete type
tcpstat foo(struct tcpstat *bar) {
return bar;
}
This didn't happen with the jaguar-missing-headers headers, so I'm not
sure... Any ideas how to fix it?
We had a working header, but seems like Apple's is a little broken.
Thanks!
You're welcome,
Kyle Moffett
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] A note to the perl module maintainers
On Thursday, Jan 2, 2003, at 02:30 US/Eastern, Hisashi T Fujinaka wrote: I subscribed myself to the cpan update list and boy, does it have a lot of traffic. I figured out how to filter on the subject line, and I'm bouncing messages for all of thesin's modules over to him. I'm just using a procmail recipe. If you want your module info bounced to you, let me know. If you can think of a better way to do this, let me know that as well. :) Sure, this would be pretty useful in keeping track of new releases: [EMAIL PROTECTED]: Freezethaw MLDBM MLDBM::Sync P.S.: I have used these modules frequently and they seem to work fine, I haven't had any errors. Thanks, Kyle Moffett --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Dec 2002 Dev Tools not installed ...
No, not. I don't think the solution needs to be so general. Isn't it sufficient to just add a conditional prompt invoked by qt3 installation as a *temporary* work around? Kow On Thursday, Jan 2, 2003, at 19:59 US/Pacific, Ben Hines wrote: On Thursday, January 2, 2003, at 07:35 PM, Kow K wrote: While this error isn't fatal, I think it would be helpful to indicate this at the beginning of the update process, with a user prompt like: Note: packages qt3-3.1.1-1 ... need Dec 2002 Developer Tools installed. Do you have it already? [y/N] We have no BuildConflicts feature yet in fink, nor do we have a pseudo package for the developer tools that the package could BuildDepend: on. Thus, build time conflicts have to be hacked out in the compile script. I think there are open feature requests for both of these. :) -Ben --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Dec 2002 Dev Tools not installed ...
On Thursday, January 2, 2003, at 11:04 PM, Kow K wrote: No, not. I don't think the solution needs to be so general. Isn't it sufficient to just add a conditional prompt invoked by qt3 installation as a *temporary* work around? The error you saw was the earliest the qt3 package has a chance to make that information known, without making changes to the fink program itself. Which is what Ben Hines was referring to -- a feature request is open to make it possible to have those conflicts readily apparent earlier in the update process. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Dec 2002 Dev Tools not installed ...
Hi, I'm reporting a minor problem and going to make a suggestion. I was in the process of fink update-all with CVS enabled (10.2.3). The update process stopped with Qt compilation, leaving the following message: [snipped] *** ERROR *** ERROR *** ERROR *** ERROR *** ERROR *** This package depends on the December 2002 or later developer tools, available by a free download at http://connect.apple.com/ (registration required). Please update your tools and then try again. *** ERROR *** ERROR *** ERROR *** ERROR *** ERROR *** ### execution of /var/tmp/tmp.0.BWZ1cg failed, exit code 1 Failed: compiling qt3-3.1.1-1 failed Yeah, that's right. I don't Dec 2002 Dev Tools installed yet. While this error isn't fatal, I think it would be helpful to indicate this at the beginning of the update process, with a user prompt like: Note: packages qt3-3.1.1-1 ... need Dec 2002 Developer Tools installed. Do you have it already? [y/N] Best, Kow --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
