Re: dpkg/install-info update

HI Justin,


On 12.07.2012, at 19:20, TheSin wrote:

> Okay guys I believe my dpkg 1.16.4.3 is ready for fink, I have it working and been running it for a while now, and I also have a full bootstrap fork that is ready to go.  I think it may need more testing, here is the list.

[...]

> Obviously with all this and the massive needed 10year old dpkg upgrade Essentials will be added, I tried to keep this down to a bare minimum, and all of this has been modelled after the current debian setup, if we want to cut reps I'm fine with that, I just tried to get us as close as possible.

I am not sure what "cut reps" means? What is a "reps"?

And what exactly does "all of this has been modelled after the current debian setup mean" ? What is "all", and how does it differ from what we have so far? Note that Fink is *not* debian, we just use dpkg, other than that, Debian policies do not apply to us. And I see no reason to imitate them in general, I consider quite some of them rather... unfortunate. Of course where Debian has developed useful new things in the past ten years, we can consider using them. But I woudn't want to change well-established old Fink behavior without a good reason.



> Apt will need an update as well, but I'd like to deal with that afterwards as it's an other major task and the current one does work with dpkg it's just not recommended.

Aye.

> 
> So now this is where I ask for all the help of core, I need testing and reporting done, I need comments and suggestion, and finally fink needs this update.

Well, then you should open a pull request on github with your changes in them, so that we can more easily review them line by line. This makes discussion easier. And also finding your work, and testing it.

> 
> NOTE: texinfo uses triggers, my bootstrap fork has a new Triggers field for info files, the version in my experimental doesn't use it so it can be tested with current dpkg and fink.

THis sentences is a bit ambiguous, since "info file" can mean two different things -- do you mean "texinfo .info file" or "fink .info file" in this sentence?
In the former case, I would interpret your sentence as saying that you added a Triggers field to the .deb that handled .info field.

In the latter case, I would understand that you added a  new field "Triggers" to the fink .info format. In that case, I would ask what it is good for, how it works etc.?


>  The version in my fork is how it should look and be used with the new dpkg/fink.  Maybe Triggers could be moved to current fink?  Also the .la file clean up code that is currently done at install via dpkg-base-files has been added to fink directly before packaging, this is so md5sums files doesn't break,

Is this "md5sums files" stuff your are talking about something we *have* to do right away, or is it something we could activate later? Because quite frankly, the fewer things we change, the easier the transition will be.

Indeed, in the same vein, it might be worthwhile to *NOT* enable (or at least, not use) "trigger" functionality at first. Only activate it once we otherwise switched to the new dpkg. That would take a bit longer, but might ease transition. Just a thought...


Max



> I know smacks wanted a switch for this, currently in my fink it just runs both but since it's done first the second one doesn't do a thing.  The reason I didn't add a switch is that every pkg needs to add it, else md5sums and deb sums pkg is useless until then.  I understand that smacks doesn't want to have different content in already made debs versus newer debs.  But in this case I can not see the harm as once installed they are identical and it fixes a major flaw in fink.  If anything I'd rather it be a config option so it's system wide versus pkg wide so users like me that want to use debsums as a cron job on all system in an env to make sure files check out we can without having to modify fink directly.
> 
> That is just a side note, but something I wanted to bring up with fink-core.
> 
> Looking forward to getting this wrapped up and helping improve fink, then I can start on apt.
> ---
> TS
> http://www.southofheaven.org/
> Life begins and ends with chaos, live between the chaos!
> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> fink-core mailing list
> [email protected]
> List archive:
> http://news.gmane.org/gmane.os.apple.fink.core
> Subscription management:
> https://lists.sourceforge.net/lists/listinfo/fink-core
> 


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
fink-core mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.apple.fink.core
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-core